On Sat, 2008-03-29 at 14:17 +0000, lcampagn wrote: > I've seen it before--my understanding is that adding the debugging > symbols changes the memory signature in the stack. So for example, > what used to corrupt some crucial memory might now just overwrite text > in a debugging symbol. Alternatively, the presence of debuggibg > symbols might slightly alter the probability of encountering a race > condition. > > I could be totally wrong here, though.. what I've seen before was due > to compiling with the -g flag vs without, I assume the dbgsym packages > do essentially the same thing.
It's my understanding that the dbgsym packages just put the symbols in a location for gdb to access when it needs them, so they don't have any effect on the program running as normal. However I may be wrong about this. Changing the stack would certainly make some bugs appear and disappear, so that is certainly a plausible explanation. Thanks, James -- segfault in hydrogen after ~5minutes of use https://bugs.launchpad.net/bugs/197809 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
