|
From: Earnie B. <ea...@us...> - 2008-08-04 17:31:04
|
Quoting Brian Dessent <br...@de...>: > Earnie Boyd wrote: > >> >> In my opinion, since MinGW cannot provide a .pdb file, >> >> windbg cannot locate error point correctly. And the main reason of >> >> system crashing also on xenvbd driver. >> > >> > MinGW (and GCC) don't use separate files for debug symbols (e.g. *.pdb >> > files). MinGW embeds the debugging information directly into object >> > files and executables. Just passing the "-g" flag to your compiler >> > invocation will cause the compiler to generate debugging information. >> >> But you can use objcopy to create a debug file. >> objcopy --only-keep-debug infile.exe outfile.dbg >> >> outfile.dbg can then be used by gdb. > > This is all true, but I think everyone is missing the point. Wayne > Gong's original complaint was that since windbg can only read the MS > format of debug info (Codeview) it was unable to provide an accurate > location of a fault, a common observation when using a debugger without > debug info. gcc cannot produce a format of debug information that > windbg can use -- whether it's embedded in the object or placed in a > separate file is totally irrelevant. > What's the purpose of --enable-extra-pe-debug? Earnie |