linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Martin Costabel <costabel@wanadoo.fr>
To: Tom Rini <tmrini@ntplx.net>
Cc: linuxppc-dev@lists.linuxppc.org, bug-gnuplot@dartmouth.edu
Subject: Re: [Patch] linuxppc gnuplot segfaults in save
Date: Thu, 15 Apr 1999 08:54:33 +0200	[thread overview]
Message-ID: <37158D29.132CCFC1@wanadoo.fr> (raw)
In-Reply-To: Pine.LNX.4.05.9904141910410.487-100000@pc.wackyland.com


Tom Rini wrote:

> Hmm.  I don't use gnuplot (and thus didn't see the bug and don't have the
> source handy), so if any x86/Linux users with glibc 2.1.x installed could
> see if they run into the bug..

When gnuplot-3.7 came out, this problem was mentioned to one of the
gnuplot discussion groups (which I don't normally read, I use gnuplot
only occasionally, with octave, for example). It didn't get much
attention, because it seems to affect only linuxppc (and who's using
that, anyway?)
 
> > Or could someone find out what's wrong with the fprintf function in
> > LinuPPC? Note that this is not specific for one version of glibc. I
> > tried it on several from glibc-961212 to glibc-2.1.1-3a. Same result.
> 
> It failed under the old libs?

Yes, I compiled gnuplot-3.7 under glibc-961212 (rev 1o, IIRC), and the
result was the same. I managed to track the problem down to the fprintf
call, but I don't know enough C and glibc to go any further.

--
Martin

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-04-15  6:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-14 22:27 [Patch] linuxppc gnuplot segfaults in save Martin Costabel
1999-04-14 23:13 ` Tom Rini
1999-04-15  6:54   ` Martin Costabel [this message]
1999-04-15  9:16     ` Franz Sirl
1999-04-15 10:47       ` Lars Hecking
1999-04-15 10:55       ` Martin Costabel
1999-04-19 18:52         ` Troy Benjegerdes
1999-04-15 12:28       ` Gabriel Paubert
1999-04-15 14:07         ` Franz Sirl
1999-04-15 16:54           ` Gabriel Paubert
1999-04-15 11:56     ` Gary Thomas
1999-04-15  7:05 ` Hans-Bernhard Broeker
1999-04-15  7:58   ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
1999-04-15 19:00 Dean Luick
1999-04-15 20:34 ` [Patch]linuxppc " David Edelsohn

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=37158D29.132CCFC1@wanadoo.fr \
    --to=costabel@wanadoo.fr \
    --cc=bug-gnuplot@dartmouth.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=tmrini@ntplx.net \
    /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 NNTP newsgroup(s).