Re: [Tinycc-devel] Windows debugger which understands tcc generated debug symbols?

[Jeremy Kvurr]

For some reason compiler creates the .stabst section, while gdb (from the mingw kit) waits for the .stabstr (with the "r" at the end). What am I doing wrong? Btw, I'm still playing with the version I downloaded from the main site, which is probably outdated a bit?

On Sun, Dec 20, 2015 at 1:51 AM, Michael Matz <address@hidden> wrote:

Hi,

On Sat, 19 Dec 2015, Jeremy Kvurr wrote:

Hello. I know about the existance of the -g option in the tcc, but I don't
know how to enable a source-level debugging using this debug info. I tried
to run the tcc-generated program with winedbg, but he hasn't recognised the
symbols it seems. And I want to know where this debugging info is placed in
the exe, and what format does it use.

It uses the stabs debugging format.  But only a very restricted subset, namely only line information (i.e. filenames, include hierarchy, function names, source line numbers).  The info is in the .stab and .stabstr sections.  gdb is able to interpret this debug format, I don't know other windows debuggers.


Ciao,
Michael.

_______________________________________________
Tinycc-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/tinycc-devel