[Bug target/27629] SIGSEGV in printstack()

2006-08-15 Thread pinskia at gcc dot gnu dot org
--- Comment #11 from pinskia at gcc dot gnu dot org 2006-08-15 18:15 --- No feedback in 3 months so closing as invalid. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/27629] SIGSEGV in printstack()

2006-05-17 Thread ebotcazou at gcc dot gnu dot org
--- Comment #3 from ebotcazou at gcc dot gnu dot org 2006-05-17 06:31 --- I cannot reproduce on the SPARC/Solaris 9 machine I use. Please provide as many details as you can on the OS, the linker, the assembler, GCC, GDB and so on. -- ebotcazou at gcc dot gnu dot org changed:

[Bug target/27629] SIGSEGV in printstack()

2006-05-17 Thread sebor at roguewave dot com
--- Comment #4 from sebor at roguewave dot com 2006-05-17 15:12 --- Here's the verbose output from the compiler driver: $ gcc -v t.c Using built-in specs. Target: sparc-sun-solaris2.9 Configured with: /build/sebor/gcc-4.1.0/configure --enable-languages=c,c++

[Bug target/27629] SIGSEGV in printstack()

2006-05-17 Thread sebor at roguewave dot com
--- Comment #5 from sebor at roguewave dot com 2006-05-17 17:43 --- I'm told that the fault is due to a known problem in the Sun libc: 6372620 printstack() segfaults when called from static function It this doesn't provide sufficient detail to work around the bug in gcc (assuming you

[Bug target/27629] SIGSEGV in printstack()

2006-05-17 Thread ebotcazou at gcc dot gnu dot org
--- Comment #6 from ebotcazou at gcc dot gnu dot org 2006-05-17 18:10 --- I'm told that the fault is due to a known problem in the Sun libc: 6372620 printstack() segfaults when called from static function It this doesn't provide sufficient detail to work around the bug in gcc

[Bug target/27629] SIGSEGV in printstack()

2006-05-17 Thread sebor at roguewave dot com
--- Comment #7 from sebor at roguewave dot com 2006-05-17 18:34 --- Maybe it's one of the runtime library functions that's static (maybe _start?). The diff between the two .s files is empty. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27629

[Bug target/27629] SIGSEGV in printstack()

2006-05-17 Thread ebotcazou at gcc dot gnu dot org
--- Comment #8 from ebotcazou at gcc dot gnu dot org 2006-05-17 20:40 --- Maybe it's one of the runtime library functions that's static (maybe _start?). Excerpt from gcc/config/sparc/sol2-c1.asm: .section.text .proc 022 .global _start _start:

[Bug target/27629] SIGSEGV in printstack()

2006-05-17 Thread sebor at roguewave dot com
--- Comment #9 from sebor at roguewave dot com 2006-05-17 21:35 --- Here's what I learned from Sun: Here is the test case from that bug report: [Makefile] main: main.o libshibby.so gcc -L. -lshibby -Wl,-R. -o main main.o main.o: main.c gcc -c -o main.o main.c

[Bug target/27629] SIGSEGV in printstack()

2006-05-17 Thread ebotcazou at gcc dot gnu dot org
--- Comment #10 from ebotcazou at gcc dot gnu dot org 2006-05-18 05:52 --- Here is the test case from that bug report: I gather than compiling with -fPIC and/or calling printstack from a shared library is necessary to trigger the bug, which is not what you reported. At this point

[Bug target/27629] SIGSEGV in printstack() on Solaris 9

2006-05-16 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-05-16 17:31 --- (In reply to comment #0) If this is due to a Solaris bug it would be great if gcc could work around it. And this attitute is wrong. Did you file this with Sun yet? If not, you should say the same thing, if this

[Bug target/27629] SIGSEGV in printstack() on Solaris 9

2006-05-16 Thread sebor at roguewave dot com
--- Comment #2 from sebor at roguewave dot com 2006-05-16 17:35 --- I'm not sure what you find wrong with my attitude but yes, I did send Sun a note about it pointing them to this problem report. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27629