linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: Dean Luick <dean@natinst.com>
Cc: costabel@wanadoo.fr, linuxppc-dev@lists.linuxppc.org
Subject: Re: [Patch]linuxppc gnuplot segfaults in save
Date: Thu, 15 Apr 1999 16:34:48 -0400	[thread overview]
Message-ID: <9904152034.AA48802@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Dean Luick <dean@natinst.com> of "Thu, 15 Apr 1999 14:00:36 CDT." <37163753.D2022EDD@natinst.com>


	You can try invoking EGCS with the additional commandline argument
-mdebug-arg for it to print out additional information about how it is
advancing through the arguments of functions and figure out where in
rs6000.c:function_arg() it is not matching what fprintf expects.  FP gets
very complicated.

David

[[ 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 20:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-15 19:00 Re:[Patch]linuxppc gnuplot segfaults in save Dean Luick
1999-04-15 20:34 ` David Edelsohn [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-04-14 22:27 [Patch] linuxppc " Martin Costabel
1999-04-14 23:13 ` Tom Rini
1999-04-15  6:54   ` Martin Costabel
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

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=9904152034.AA48802@marc.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=costabel@wanadoo.fr \
    --cc=dean@natinst.com \
    --cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).