| View previous topic :: View next topic |
| Author |
Message |
EmrldDrgn
Joined: 20 May 2009
Posts: 4
|
 Posted: Sun May 24, 2009 4:32 pm Post subject: Program crashing, but not in psp-gdb |
 |
|
| I'm chasing a crasher bug, but it doesn't occur when psp-gdb is connected, even if there are no breakpoints or anything. I know in a "normal" situation I could postmortem debug it, but I can't seem to find a way to do so on a PSP. Is there a way to either a), postmortem debug on a psp, or b), tell psp-gdb to stop padding things and/or default-initializing things to some value? (those are the only two reasons I can think of why gdb would stop a crash from happening). I can find information on neither of these things using google. |
|
| Back to top |
|
 |
TyRaNiD
Joined: 18 Jan 2004
Posts: 918
|
| Posted: Mon May 25, 2009 11:04 pm Post subject: |
|
|
| psp-gdb shouldn't do anything to your application, there is no concept of a "debugging" version of a process. And about the only way to post-mortem debug is wait for the crash to occur in psplink and use its internal debug features to see what went wrong. Of course if it is not dying in gdb is it even dying in psplink? |
|
| Back to top |
|
|
sauron_le_noir
Joined: 05 Jul 2008
Posts: 229
|
| Posted: Sat May 30, 2009 5:51 am Post subject: |
|
|
look at variables that are not initialize. When running under a gnu debugger normaly the uninitialized memory is padded with 0x0 values.
char *p
if (p == NULL)
under debug it is ok p is set to 0x0 but if not under debug the value of p
is what you have in your memory |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
