Your message dated Tue, 24 Oct 2006 12:16:22 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Compiler issue
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gdb
Version: 6.4.90.dfsg-1
The etch version of gdb seems to have a bug where it does not
attach a break point to the correct line.
I have not experienced that bug before upgrading to etch,
and it is present for both the gcc 4 and gcc 3 compilers,
therefore I think the bug is really in gdb.
$ pr -n main.c
1 int main(int argc, char *argv[])
2 {
3 int c;
4
5 if (0)
6 goto failure;
7
8 c = 1;
9
10 failure:
11 return 0;
12 }
$ gcc -O0 -g -o main main.c
$ gdb main
GNU gdb 6.4.90-debian
...
(gdb) b main.c:6
Breakpoint 1 at 0x8048354: file main.c, line 6.
(gdb) r
Starting program: /home/cfischer/tmp/main
Breakpoint 1, main (argc=1, argv=0xafb3bfa4) at main.c:8
8 c = 1;
(gdb) quit
--
Claus Fischer <[EMAIL PROTECTED]>
http://www.clausfischer.com/
--- End Message ---
--- Begin Message ---
Closing this; no GDB bug here, but suboptimal debug info.
--
Daniel Jacobowitz
CodeSourcery
--- End Message ---
