| View previous topic :: View next topic |
| Author |
Message |
Anonymous
Guest
|
 Posted: Thu Jun 02, 2005 10:18 am Post subject: Running SDBG with code compiled with /undef |
 |
|
| When using code compiled with /undef, SDBG crashes if it encounters an undefined variable but doesn't stop at or indicate where the offending line is. The crash message from running outside SDBG gives a full stack as expected. |
|
| Back to top |
|
 |
Anonymous
Guest
|
| Posted: Fri Jun 03, 2005 2:10 am Post subject: Running SDBG with code compiled with /undef |
|
|
| That certainly should not be the case. Can you debug your program normally before the undefined variable? Do you have details of the sdbg crash? |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Tue Aug 02, 2005 3:27 am Post subject: Running SDBG with code compiled with /undef |
|
|
Hi Rob,
Joe lost his account details so I'm picking up the ball!
SDBG itself doesn't crash, but the displayed 'stack' doesn't show where the application crash occurred. The program can be stopped at the line that causes the access violation, but then stepping past it wipes out the stack.
What can I send you so you can follow this up?
Best Regards
Kenny Tilley |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
