This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/54012] printf crash with -lgfortran
- From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 30 Oct 2012 17:57:51 +0000
- Subject: [Bug libfortran/54012] printf crash with -lgfortran
- Auto-submitted: auto-generated
- References: <bug-54012-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54012
--- Comment #8 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2012-10-30 17:57:51 UTC ---
> > > > What does gdb tell you?
> > >
> > > gdb tells:
> > >
> > > Program received signal SIGSEGV, Segmentation fault.
> > > 0x00007ffff779f8f2 in __parse_one_specmb () from /lib64/libc.so.6
> > >
> >
> > Not very helpful. What does gdb tell you when you
> > compiler with the -g option and issue bt at the gdb
> > prompt?
>
> (gdb) run
> Starting program: /home/seger/TEMP/10/a.out
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff779f8f2 in __parse_one_specmb () from /lib64/libc.so.6
> (gdb) bt
> #0 0x00007ffff779f8f2 in __parse_one_specmb ()
> from /lib64/libc.so.6
> #1 0x00007ffff7781230 in vfprintf () from /lib64/libc.so.6
> #2 0x00007ffff778b179 in printf () from /lib64/libc.so.6
> #3 0x000000000040051a in main () at 1.c:4
>
This does not look like a libgfortran issue. Do you have
valgrind on your system? Can you run the good and bad
executable under valgrind? This appears to be a buffer
issue in your libc.