User forums > Nightly builds

The 18 June 2006 build is out.

<< < (4/12) > >>

Denis:
I can't debug programm with this nightly build.
I created new console project, built it, set break point to "std::cout << "Hello world!" << std::endl;" line and pressed "Debug / Continue" button. Then I got debugger message "No source file named d:/GCC/test2/main.cpp". What I did wrong? Last time I tryed RC2, it worked without problem.

PS: WinXP SP2, MinGW 3.4.2 

kkez:

--- Quote from: thomas on June 19, 2006, 03:32:46 pm ---
--- Quote from: kkez on June 19, 2006, 02:44:16 pm ---
--- Quote from: thomas on June 19, 2006, 01:41:17 pm ---If you press "Abort", the crash handler will simply return control to the system exception handler (reading what's displayed in the message helps), so after you do that, the application *will* crash.
--- End quote ---
That's not true, after clicking two or three times on abort C::B doesn't crash.
--- End quote ---
What makes you say that?

--- End quote ---
It doesn't crash on some circunstances, when it's really not the place for a crash (ie the example i made before, inside the openfilename dlgbox. I can prove it if you want, what did you use to make that gif?

MortenMacFly:

--- Quote from: Denis on June 19, 2006, 05:42:36 pm ---I can't debug programm with this nightly build.

--- End quote ---
You'll need at least GDB version 6.3. Search the forum for this keyword for additional information.
With regards, Morten.

Michael:

--- Quote from: Denis on June 19, 2006, 05:42:36 pm ---[...]MinGW 3.4.2

--- End quote ---

Hello,

I would advice you to also upgrade GCC to 3.4.4 or 3.4.5.

Best wishes,
Michael

Pecan:

--- Quote from: kkez on June 19, 2006, 02:44:16 pm ---
--- Quote from: thomas on June 19, 2006, 01:41:17 pm ---If you press "Abort", the crash handler will simply return control to the system exception handler (reading what's displayed in the message helps), so after you do that, the application *will* crash.
--- End quote ---
That's not true, after clicking two or three times on abort C::B doesn't crash.

BTW, i always get a crash handler dialogbox doing this:
1) File->Open...
2) create a new folder
3) insert a name and press enter
4) click 3 or 4 times on "Abort", C::B will continue to run


--- End quote ---

Is there a possibility that this behavior is caused by the SIGTRAP's that are buried in ntdll.dll?
When running CodeBlocks under GDB, I get these traps when using system calls such as open/save/etc.
A simple C continues GDB and the program continues.

This sounds like what is happening. Just a guess.

Navigation

[0] Message Index

[#] Next page

[*] Previous page