Your message dated Wed, 16 May 2012 21:43:31 +0100
with message-id
<CAPQ4b8=bovvrqz4tf4odphn-pm+u9hh23qshdko_qu+-_y_...@mail.gmail.com>
and subject line Re: Regression: Even with -O0 -g, gcc 4.1 optimizes a goto
away and I cannot debug
has caused the Debian Bug report #395057,
regarding Regression: Even with -O0 -g, gcc 4.1 optimizes a goto away and I
cannot debug
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
395057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=395057
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc
Version 4.1.1-11
In the following sample code, gcc does not create enough
debugging information to let gdb break in lines 27, 30, 33, 36.
This makes debugging the main() function extremely painful.
This is a regression from gcc 2.95 and gcc 3.3, both of which
let gdb set a breakpoint on those lines.
The ability to debug such code is very important to me, since
I usually write my C functions with some cleanup code
after a 'failure' label in the style below.
1 int f1(void) /* this "succeeds", i.e. returns 1 */
2 {
3 return 1;
4 }
5
6 int f2(void) /* this "succeeds", i.e. returns 1 */
7 {
8 return 1;
9 }
10
11 int f3(void) /* this "fails", i.e. returns 0 */
12 {
13 return 0;
14 }
15
16 int f4(void) /* this "succeeds", i.e. returns 1 */
17 {
18 return 1;
19 }
20
21
22 int main(int argc, char *argv[])
23 {
24 int c;
25
26 if (!f1())
27 goto failure;
28
29 if (!f2())
30 goto failure;
31
32 if (!f3())
33 goto failure;
34
35 if (!f4())
36 goto failure;
37
38 success:
39 return 0;
40
41 failure:
42 return 1;
43 }
--
Claus Fischer <claus.fisc...@clausfischer.com>
http://www.clausfischer.com/
--- End Message ---
--- Begin Message ---
fixed 395057 4.4.0-1
stop
Hello,
Thanks for the detailed bug reports and your interest in improving
Debian. Sorry that the bug was unattended for so long. I'm just
doing some cleanup, I am not involved with the GCC package.
This bug seems to have been fixed upstream a while ago, marking it as
such and closing.
Please reopen the bug if you find that it's still happening.
Cheers.
--- End Message ---
