Debugger Hanging

[sorinev]

I have a small C project where when I get to my breakpoint, the entire program becomes non-responsive, debugger and all. At first I thought maybe it was the most recent build (9492, I build from source), but it's showing the exact same behavior in 12.11 also. Is there anything I can do to find out why it becomes permanently non-responsive? I mean if it was crashing that's one thing, but it's going "Not Responding." Windows 7 64-bit.

[oBFusCATed]

Does this happen for a hello world project?
Do you have the local variables and function arguments enabled. Does it work if you disable them?

[sorinev]

I haven't tried with a hello world program, but it does still do it with locals and function args turned off after I add the array I need watched. Maybe it doesn't like the array being 32768 elements.

[oBFusCATed]

You've not mentioned that you have a watch for an array... This is known to be slow, don't do it, just inspect the part of the array you're interested in.

[sorinev]

That's exactly what I was trying to do, only watch a small portion (about 6-8 elements). But as soon as I clicked on the watch window to add a new line (the small portion), it stopped responding. I think it may be because that array was a local, so it was already in the watch window under that section.

[ollydbg]

1, you can limit GDB to show the element size, the command I use is:

Code

set print elements 200

2, you can debug the same program in the Windows Command Line, and show us the log messages. Maybe your variable is un-initialized, we have discussed already about un-initialized local variables issues in our forum.