tinycc-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Tinycc-devel] debug info broken


From: foobar
Subject: [Tinycc-devel] debug info broken
Date: Sun, 17 Dec 2017 22:30:37 +0000

Hi list,

First of all, thanks for the release!
I've built 0.9.27 for x86_64 and tried a see if debugging works, but:

$ cat true.c 
int main() { return 0; }

$ tcc true.c -g -o true
$ gdb ./true
GNU gdb (GDB) 7.6.2
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from ./true...DW_FORM_strp pointing outside of .debug_str 
section [in module /home/rofl/hardcore-utils/true]
done.
(gdb) b main
Breakpoint 1 at 0x0 (2 locations)
(gdb) l
1       int main() { return 0; }
2
(gdb) r
Starting program: ./true 
warning: no loadable sections found in added symbol-file system-supplied DSO at 
0x7ffff7ff9000
Warning:
Cannot insert breakpoint 1.
Error accessing memory address 0x0: I/O error.

(gdb) q
A debugging session is active.

        Inferior 1 [process 19218] will be killed.

Quit anyway? (y or n) y


Is this expected ? unimplemented ? a bug only in x86_64 ?
IMO the perfect niche for using TCC is for development, since you can rebuild 
entire projects in the fraction of time it takes with GCC, but if debugging the 
result is impossible, that's quite a bummer.

BTW: is there an IRC channel ?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]