Related articles |
---|
libdwarf compiled on windows torleif.sandnes@broadpark.no (Torleif Sandnes) (2003-10-06) |
From: | Torleif Sandnes <torleif.sandnes@broadpark.no> |
Newsgroups: | comp.compilers |
Date: | 6 Oct 2003 21:26:10 -0400 |
Organization: | Compilers Central |
Keywords: | linker, debug, question |
Posted-Date: | 06 Oct 2003 21:26:10 EDT |
Hi.
I recently downloaded the source code for the libdwarf library and the
dwarfump tool, and tried to execute dwarfdump on an elf/dwarf object
file compiled with gcc on linux.
dwarfdump failed with the message:
./dwarfdump -l ../../../downloaded/object.o
.debug_info
./dwarfdump ERROR: attempting to print .debug_info:
DW_DLE_CU_LENGTH_ERROR (47) (47)
attempting to continue.
I also tried to initialize the dwarf library, using the elf library.
The frst call to dwarf_next_cu_header() results in the same error:
DW_DLE_CU_LENGTH_ERROR (47)
My three questions are:
1. Is there a tool to produce dwarf debug information on windows.
(I could not get cygwin's gcc to produce dwarf)
2. Does anybody know how to get the dwarf library to work on windows?
Or does anybody have any conjectures on what the problem might be.
3. Is there a well known, (and obvious ), problem with producing object
files with gcc on linux running on an intel 386 comp. processor and
then parsing these object files using libelf and libdwarf compiled for,
and running on a windows i386 platform?
Regards
Torleif Sandnes
Return to the
comp.compilers page.
Search the
comp.compilers archives again.