Stack traces and sections
Mon Feb 2 15:41:00 GMT 2009
On Mon, Feb 02, 2009 at 04:24:11PM +0100, Piotr Wyderski wrote:
>I would like to add stack traces to my program. I've already implemented
>a stack walker, but there is an open problem with symbol name/line lookup.
>The compiler (GCC 4.4-trunk) emits DWARF2-compatible debug information,
>but I don't know how to reach the appropriate sections (especially
>within the executable. The PE header walker is able to dump PE sections, but
>they have strange, numeric names, e.g.:
>sec: name = .text
>sec: name = .data
>sec: name = .rdata
>sec: name = .bss
>sec: name = .idata
>sec: name = /4
>sec: name = /19
>sec: name = /35
>sec: name = /47
>sec: name = /61
>sec: name = /73
>sec: name = /86
>sec: name = /97
>sec: name = /108
>On the other hand, the DWARF sections are available in the file -- a hexdump
>viewer can locate them, as well as objdump. Could somebody please tell me
>what should I do in order to get to the DWARF sections from this point?
>Any documentation will be appreciated.
Sorry but this isn't the right mailing list for this question.
This mailing list is for the discussion of development of the Cygwin DLL and
This actually isn't even a Cygwin-specific question, AFAICT. You'd
probably be better served in a Microsoft-specific mailing list.
More information about the Cygwin-developers