User forums > Help

Problems using C::B / GDB under WinXPSP2

<< < (2/2)

thomas:
Hmm... I have no experience with a debugger running on virtual memory, but could that possibly be a cause? In theory, VM management should be 100% transparent to an application, but is that true for a debugger, too?

256 MB is not really a lot for Windows XP SP2, the system almost eats up that much already. Code::Blocks has a working set of ~25MB too, and neither compiler nor debugger are what you would call lightweight processes. So maybe the debugger produces errors because of some strange VM issue when something is paged? Just an idea...

Do you have another machine with more RAM, and can you reproduce the problems there?

Urxae:

--- Quote from: thomas on October 19, 2005, 01:45:41 pm ---Hmm... I have no experience with a debugger running on virtual memory, but could that possibly be a cause? In theory, VM management should be 100% transparent to an application, but is that true for a debugger, too?

--- End quote ---

Should be totally transparent, unless timing is involved. Then things get wacky ;).
Well, except for the fact that memory requests tend to be denied less often, but that should usually hide bugs, not reveal them...

Diego:
Hi All!

Well, I've been trying most of what you said and other tricks but there was no success.

I' ve tried downgrading the GDB to v5.2 and the problems is still the same. I've tried step into instead of step over and again, no
success.

Just to give you more info, the line where I put the breakpoint contains a call to a function in other module, I tried putting
the breakpoint inside that function in that module, and again it crashes. It seems to be a problem when the breakpoint is in
some way related to other module than 'main'.

Regarding the RAM issue, that's right 256MB is not big deal, but I think we can rely on the MS VM implementation... can we?
Anyway I gave the project to a friend who's PC is more powerful than mine and the same "bug" appears.

The good thing, unless for C::B, is that some other IDEs based on GDB (like C-Free or Dev-C++) also fail to debug the program. The
difference is that with C::B we can get more info from the GDB (Debug) log window  :)

I will try to set up a basic case where this 'bug' appears and will send it to you, but first I have to finish my programming project  :? !!

Thank you!
Diego.

rickg22:
Diego: When you can't debug, you have to use the last resort: MessageBoxes, printf's, etc!

We've pinpointed nasty bugs in C::B using this primitive-but-effective method.

Diego:
Hi all again,

Well it seems now I can tell more about the problem.

I redesigned my hole project because it was a "little" time and memory consuming, the latter was, I think, terrible. :lol:

For now I don't have that nasty problem while debugging.

I guess that I was overloading in some way the debbuger by asking it to handle big structures that might have entered in conflict with the memory management.

Although in a perfect world this should be transparent I guess we can't be so demanding :shock:

Thank you all for your help!
Goodbye!

Navigation

[0] Message Index

[*] Previous page