From: Stephen Turner <S.R.E.Turner@statslab.cam.ac.uk>
To: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
Cc: "Marco d'Itri" <md@Linux.IT>, Michel Lanners <mlan@cpu.lu>,
debian-powerpc@lists.debian.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: Bug#86356: analog: analog segfaults
Date: Fri, 23 Feb 2001 21:59:39 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.3.96.1010223213706.8247B-100000@gamma.statslab.cam.ac.uk> (raw)
In-Reply-To: <01022316292300.06063@localhost>
On Fri, 23 Feb 2001, Kevin B. Hendricks wrote:
>
> Here is a quick and dirty way to test. Move both double parameters to the
> beginning of the function and caller and the problem should go away.
>
> Another solution is to include a "dummy" int variable in both the caller
> and the function right before the double parameter "unit". That dummy will
> fill a stack slot and force any messed up double alignment issue to become
> moot.
>
The second fix got it past the call to printtree(). Then it crashed when
calling another function, printcols(), which I fixed with the first fix.
This allowed it to run without crashing, but the resultant output was
obviously wrong, with what could have been a related bug.
Anyway, I think this proves that your hypothesis was correct.
> If either of those workarounds work, then please pass all of this info to
> Franz Sirl's attention on the gcc@gcc.gnu.org site and he can use it to
> track down the messed up code. It the workarounds fix things, this is a
> definite bug
>
You said these were mostly fixed in the 2.95.3 series. The original bug
filer is using 2.95.2. Should I still file a bug? Or has someone got a
nightly build or something that they could test it on first, in case it's
already been fixed?
--
Stephen Turner http://www.statslab.cam.ac.uk/~sret1/
Statistical Laboratory, Wilberforce Road, Cambridge, CB3 0WB, England
"Your account can only be used for a single internet session at any one
time and for no more than 24 hours in any one day." (NTL terms of use)
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-23 21:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010223195620.F4145@wonderland.linux.it>
2001-02-23 20:46 ` Bug#86356: analog: analog segfaults Stephen Turner
2001-02-23 21:29 ` Kevin B. Hendricks
2001-02-23 21:59 ` Stephen Turner [this message]
2001-02-23 22:44 ` Kevin B. Hendricks
2001-02-23 22:10 ` Andrew Sharp
2001-02-23 23:30 ` Kevin B. Hendricks
2001-03-02 10:29 ` Stephen Turner
[not found] ` <Pine.LNX.3.96.1010302101639.19312B-100000@gamma.statslab.c am.ac.uk>
2001-03-02 12:07 ` Franz Sirl
2001-03-03 15:19 ` Matthias Klose
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=Pine.LNX.3.96.1010223213706.8247B-100000@gamma.statslab.cam.ac.uk \
--to=s.r.e.turner@statslab.cam.ac.uk \
--cc=debian-powerpc@lists.debian.org \
--cc=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=md@Linux.IT \
--cc=mlan@cpu.lu \
--cc=sret1@cam.ac.uk \
/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).