This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

3.2.2 symbols problem. Was it dealt with?


Hi, I've looked through the archive and not noticed
a bug report similar to what I saw in GCC 3.2.2,
so I'd like to ask if you noticed the following phenomenon:

Compile this as test.c:

#include <unistd.h>

void foo(){
  int bar = 22; 
  printf("baz! %d\n",bar); 
  pause();
}
void baz(){
  foo();
}
main(){
  baz();

}

Use "gcc -g -o test test.c".

Open it with GDB, run it, and do a ctl-C.

You'll get this stack trace:

0xffffe002 in ?? ()
(gdb) where
#0  0xffffe002 in ?? ()
#1  0x0804838e in baz () at test.c:10
#2  0x080483a5 in main () at test.c:13
#3  0x420156a4 in __libc_start_main () from /lib/tls/libc.so.6
(gdb) q

Notice how the stack trace omits any mention of foo(). 

Can I reliably tell my overlords that 3.2.3 or 3.3 are free of this bug?

Thanks in advance. 




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]