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

2015-12-24 Thread 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

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

2015-12-19 Thread Jeremy Kvurr
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

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

2015-12-19 Thread Michael Matz
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