LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: md@linux.it
Cc: debian-powerpc@lists.debian.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: [S.R.E.Turner@statslab.cam.ac.uk: Re: Bug#86356: analog: analog segfaults]
Date: Thu, 22 Feb 2001 07:55:48 +0100 (CET)	[thread overview]
Message-ID: <200102220655.HAA00821@piglet.grunz.lu> (raw)
In-Reply-To: <20010220160910.B20027@attila.bofh.it>


[cross-posted to linuxppc-dev]

On  20 Feb, this message from md@linux.it echoed through cyberspace:
> Background: analog segfaults when using a custom config file.
> The author tried debugging the program on my B50 and replied with this
> message.
> Is gcc known to be buggy for powerpc? I'm running 2.95.2-17 and the
> program has been compiled without optimizations.

No idea whether it _is_ buggy or not. However, the list of arguments to
that function below seems rather long to me, so if it is a bug in gcc,
it might not have been noticed before.

Anyway, one thing to look at might be the fact that not all function
arguments are passed the same way according to the ABI we are using. The
first few are passed in registers, the rest on the stack (IIRC).
However, I don't know exactly how many are passed in registers. But it
would seem that 22 (the arguments coming through OK below) is a bit high
a number...

Any of the gcc gurus around?

Michel

> ----- Forwarded message from Stephen Turner <S.R.E.Turner@statslab.cam.ac.uk> -----
>
> OK, I've discovered what's going on, but I have no idea WHY it's going on.
>
> The problem comes at line 736 of output.c. That line calls printtree, as
> follows:
>
> printtree(outf, rep, outstyle, multibyte, tree, requests, date, badp, badn,
>           0, NULL, aliashead, linkhead, baseurl, totr, totp, totb, width,
>           possrightalign, bmult, unit, sepchar, repsepchar, decpt, compsep,
>           rawbytes, cols, colhead, colheadp, gender, html, monthname,
>           dayname, monthlen, daylen, plainmonthlen, plaindaylen, lngstr);
>
> But by the time we reach printtree, several of the values are wrong.
> Everything is fine up to unit. But sepchar got repsepchar's true value (0),
> repsepchar got decpt's true value ('.'), etc., until plaindaylen got
> lngstr's value (0x100e93c0 = 269390784) and lngstr got a random value.
>
> As I say, I don't really see how this can have happened. Have you
> encountered anything like this before?
>
> ----- End forwarded message -----


-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2001-02-22  6:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010220160910.B20027@attila.bofh.it>
2001-02-22  6:55 ` Michel Lanners [this message]
2001-02-23 16:05   ` [S.R.E.Turner@statslab.cam.ac.uk: Re: Bug#86356: analog: analog segfaults] Kevin B. Hendricks
2001-02-23 16:08   ` Jerry Van Baren

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=200102220655.HAA00821@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --cc=debian-powerpc@lists.debian.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=md@linux.it \
    /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