RE: [GD-Windows] Finding routine that's crashing
Brought to you by:
vexxed72
From: Brian S. <bs...@mi...> - 2002-07-31 19:22:56
|
StackWalk() gives you the stack trace. Robbins' Debugging Windows Apps covers this in some detail as well. It doesn't give you anything that you won't get from inside the debugger though - it's most useful for logging crashes on customer or QA machines. --brian > -----Original Message----- > From: Rich [mailto:leg...@xm...]=20 > Sent: Wednesday, July 31, 2002 12:16 PM > To: gam...@li... > Subject: Re: [GD-Windows] Finding routine that's crashing=20 >=20 >=20 >=20 > In article <555...@gu...>, > Ben Carter <be...@gu...> writes: >=20 > > [...] We've got an exception > > handler in our current project that can do a stack trace and reports > > everything it finds, with symbols if available - if you can't track > > down the information give me a shout and I'll see if I can=20 > extract the > > relevant code snippets for resolving the addresses.=20 >=20 > This would be very handy, if you're willing to share! >=20 > I can find SymGetSymFromAddr in MSDN, but I'm fuzzy on how you get the > stack trace. |