You didn't specify what compiler you were using to build the debug sources
you cared about. Keep in mind you won't be able to look through the system
libraries for things, but you'll be able to look at what you built at least.
-eric
On Mon, Nov 16, 2015 at 12:16 PM Vincent Torri <vincent.torri at gmail.com>
wrote:
> afaik, gnu windows toolchain stores debug informations in DWARF
> format. Am I wrong ?
>> Vincent Torri
>> On Mon, Nov 16, 2015 at 8:44 PM, Eric Christopher <echristo at gmail.com>
> wrote:
> > As a quick note, you're aware that Windows in general doesn't use dwarf
> > right?
> >
> > -eric
> >
> > On Mon, Nov 16, 2015 at 11:26 AM Vincent Torri <vincent.torri at gmail.com>
> > wrote:
> >>
> >> Hello
> >>
> >> I have begun to write a valgrind-like on Windows, and I use libbfd to
> >> get the stack trace (file, function and line of a frame).
> >>
> >> I would like to use libdwarf for that. But I need to port libdwarf to
> >> Windows.
> >>
> >> On the website, it is said to contact this mailing list before
> >> contributing any code.
> >>
> >> So what I suppose to do ? :-)
> >>
> >> regards
> >>
> >> Vincent Torri
> >> _______________________________________________
> >> Dwarf-Discuss mailing list
> >> Dwarf-Discuss at lists.dwarfstd.org> >> http://lists.dwarfstd.org/listinfo.cgi/dwarf-discuss-dwarfstd.org>-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dwarfstd.org/private.cgi/dwarf-discuss-dwarfstd.org/attachments/20151116/6aa293ac/attachment.htm>