After commit "local scope for types of function parameters" debugging
does not work any more.
If I compile:
#include
int main(void)
{
printf("Hello World\n");
return 0;
}
And start gdb and try to set break on main I get:
invalid dwarf2 offset 0x
If I revert the tccdbg.c change (
Finally figured out how to get gdb to display source code and step
through a tcc-compiled program. The trick is to do the compiling with
tcc -c -g and then use gcc -g for the linker bits.
$ tcc -c -g g.c
$ gcc -g g.o -o g
windows exe on linux can be made with mingw and debugged with winedbg
I had
Simon Lehmayr wrote:
Hi,
what debugger can I use to debug tcc compiled .exe files?
Since tcc uses the stabs debug info format gdb should do - but I can't
read variable contents using gdb. Breakpoints work.
Lauterbach debugger can debug stabs-using exe files, too, but also can't
read variable t
Hi,
what debugger can I use to debug tcc compiled .exe files?
Since tcc uses the stabs debug info format gdb should do - but I can't
read variable contents using gdb. Breakpoints work.
Lauterbach debugger can debug stabs-using exe files, too, but also can't
read variable type information.
What
Hello,
What debuggers work with tcc programs when I don't have the option to
use the run feature?
I tried openwatcom - but I didn't get any symbols (compiled using -g
option though).
Greetings,
Simon
___
Tinycc-devel mailing list
Tinycc-devel@non
