[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to Read debug information
From: |
Paul Pluzhnikov |
Subject: |
Re: How to Read debug information |
Date: |
Fri, 25 Nov 2005 21:46:29 -0800 |
User-agent: |
Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, linux) |
"Siegfried" <siegfried@heintze.com> writes:
> Is there compiler switch to make the compiler emit XML for each class,
> union or struct it injests?
No. However, there is this project:
http://www.gccxml.org/HTML/Index.html
> Is there an example program that will read an executable image or .o
> file and extract the type information stored there for the debugger?
There are multiple debugging formats: STABS, DWARF, DWARFv2 and v3.
The DWARF formats are current default for gcc on ELF platforms.
The format specification is here:
http://www.eagercon.com/dwarf/dwarf3std.htm
It is quite complicated, but you can get an idea of how things are
structured by compiling several simple examples, and studying output
from "readelf -w a.out"
It is quite doubtful that you'll be able to read executable image
and extract type info without significant effort.
However, libdwarf could help you quite a bit:
http://reality.sgi.com/davea/dwarf.html
Cheers,
--
In order to understand recursion you must first understand recursion.
Remove /-nsp/ for email.