public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "astroseger at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/54012] printf crash with -lgfortran
Date: Tue, 30 Oct 2012 22:37:00 -0000 [thread overview]
Message-ID: <bug-54012-4-IXjqUjFe0J@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54012-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54012
--- Comment #11 from Sergey Rodionov <astroseger at gmail dot com> 2012-10-30 22:37:40 UTC ---
(In reply to comment #10)
> (In reply to comment #9)
> > "ldd bad":
> > linux-vdso.so.1 => (0x00007fffd97ff000)
> > libquadmath.so.0 => /usr/lib64/libquadmath.so.0 (0x00007f74e80ec000)
>
> Could you try linking libquadmath directly instead of libgfortran (which
> implies libquadmath)?
>
>
> The reason is that libquadmath installs, if possible, GLIBC's printf hooks, cf.
> http://gcc.gnu.org/onlinedocs/libquadmath/quadmath_005fsnprintf.html
> and the source code at
> http://gcc.gnu.org/viewcvs/trunk/libquadmath/printf/quadmath-printf.c?view=markup
>
> With those hooks, "printf("%Qe\n", float128_number)" will work. In principle,
> it shouldn't cause those issues, but depending on the GLIBC version it might.
>
>
> (If libquadmath is the cause, it also explains that it works with -static as
> libgfortran only statically links libquadmath if needed.)
Yes. you are right. The real problem is libquadmath. If I compile with
-lquadmath it crash...
But interesting that quadmath_snprintf by itself works...
next prev parent reply other threads:[~2012-10-30 22:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 10:59 [Bug libfortran/54012] New: printf crush " astroseger at gmail dot com
2012-10-29 23:32 ` [Bug libfortran/54012] " mpolacek at gcc dot gnu.org
2012-10-30 0:34 ` kargl at gcc dot gnu.org
2012-10-30 9:52 ` [Bug libfortran/54012] printf crash " astroseger at gmail dot com
2012-10-30 9:57 ` astroseger at gmail dot com
2012-10-30 10:47 ` mpolacek at gcc dot gnu.org
2012-10-30 13:21 ` sgk at troutmask dot apl.washington.edu
2012-10-30 14:04 ` astroseger at gmail dot com
2012-10-30 17:58 ` sgk at troutmask dot apl.washington.edu
2012-10-30 19:35 ` astroseger at gmail dot com
2012-10-30 22:04 ` burnus at gcc dot gnu.org
2012-10-30 22:37 ` astroseger at gmail dot com [this message]
2013-06-23 13:35 ` [Bug libquadmath/54012] " dominiq at lps dot ens.fr
2014-10-08 15:28 ` fxcoudert at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-54012-4-IXjqUjFe0J@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).