User forums > Using Code::Blocks

Debugging code Help

<< < (4/5) > >>

Дмитро:
Again. I did not set a breakpoint. I just want to go through the code. Why debugger stops YOURSELF ??? How to avoid this?

BlueHazzard:
What is the cause of the stop? There should pop up a yellow window with something wtitten in it, like SIGTRAP or SIGSEGV, this should also be written in the debugger log...

If the cause is SIGSEGV then your program deletes or accesses an invalid pointer at the point where the debugger stoped
if the cause is SIGTRAP: http://stackoverflow.com/questions/3475262/what-causes-a-sigtrap-in-a-debug-session http://stackoverflow.com/questions/11790321/gdb-debugging-application-termintes-with-sigtrap ecc..

i did not understand your other posts... Does debugging work now? Where the cyrillic letters/ white spaces the problem?

greetings

Дмитро:
Thank you!!

Yes, it works well in general. I do see it work!

... But some of the problem is .. The disadvantage of causing a large .. Now write glue and screens.







Before it does, I've seen - a record for an array boundary. Mistakes are the former, I corrected. I quickly saw them and quickly corrected. Debugging is a great help, friendly nice tool!

But now I do not see any errors. The present circumstances.

They have a right good code, properly removed, the code is written correctly!

Stop should not be. No signs, I do not see and do not understand why all of a sudden stops here.

Дмитро:
I think it is actually the same!

https://stackoverflow.com/questions/1621059/breakpoints-out-of-nowhere-when-debugging-with-gdb-inside-ntdll

BlueHazzard:
you can use this http://stackoverflow.com/a/1691025 in Settings->Debugger->GDB debugger->Default->Debugger initialization commands

greetings

Navigation

[0] Message Index

[#] Next page

[*] Previous page