Re: Problems getting stack trace for VC6 build
- From: Matthew Gertner <matthew.gertner@xxxxxxxxx>
- Date: 29 May 2007 05:29:12 -0700
On May 29, 11:54 am, "Oleg Starodumov" <com-dot-debuginfo-at-oleg>
wrote:
Try to run the application under ExcepMon sample debugger available here:http://www.debuginfo.com/examples/dbgexamples.html
Will it be able to show source line information? (E.g. make the app raise
an artificial exception and see how ExcepMon reports the callstack)
Do I need VS.NET 2005 to compile your examples? I downloaded the
latest version of dbghelp.h from MSDN and it seems to use header files
annotations that aren't defined in the VC 7.1 header files (e.g.
__out_bcount_opt).
Is there anything in Solution Properties | Common Properties | Debug Source Files |
"Do not look for these source files" setting ?
Yes, as a matter of fact two of the files that are causing problems
are located there (along with some other files). What exactly does
that mean?
Cheers,
Matt
.
- References:
- Problems getting stack trace for VC6 build
- From: Matthew Gertner
- Re: Problems getting stack trace for VC6 build
- From: Oleg Starodumov
- Re: Problems getting stack trace for VC6 build
- From: Matthew Gertner
- Re: Problems getting stack trace for VC6 build
- From: Oleg Starodumov
- Problems getting stack trace for VC6 build
- Prev by Date: Re: Problems getting stack trace for VC6 build
- Next by Date: Re: Problems getting stack trace for VC6 build
- Previous by thread: Re: Problems getting stack trace for VC6 build
- Next by thread: Re: Problems getting stack trace for VC6 build
- Index(es):
Loading