All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: "Boehm, Hans" <hans_boehm@hp.com>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Program counter from sigcontext, constructors
Date: Sat, 26 Apr 2003 12:08:29 -0400	[thread overview]
Message-ID: <20030426160829.GE8269@systemhalted> (raw)
In-Reply-To: <200304252137.h3PLb16r014226@hiauly1.hia.nrc.ca>

> > spe170> cc -fPIC -g constr.c
> > spe170> ./a.out
> > Segmentation fault
> 
> I'm unable to duplicate this on gsyprf11.  I tried several gcc versions.
> I'm using glibc 2.3.1-15.  ld is version 2.13.90 20030210.
> 

Which versions did you try? :)

bash-2.05b$ gcc-3.0 -fPIC -g test-fpic.c; ./a.out
Segmentation fault

GNU ld version 2.13.90.0.18 20030121 Debian GNU/Linux

Reading specs from /usr/lib/gcc-lib/hppa-linux/3.0.4/specs
Configured with: ../src/configure -v --enable-languages=c,c++,f77,objc
--prefix=/usr --infodir=/share/info --mandir=/share/man --enable-shared
--with-gnu-as --with-gnu-ld --with-system-zlib --enable-long-long
--enable-nls --without-included-gettext --disable-checking
--enable-threads=posix --with-cpp-install-dir=bin --enable-objc-gc
hppa-linux
Thread model: posix
gcc version 3.0.4

Crashes under 3.0.4, looks like the possible PIC register bug we saw
with the double printf. I recommend you move to a newer gcc if possible.
I spent a few minutes looking at assembler output and %r19 looks to low
to be valid...

c.

  reply	other threads:[~2003-04-26 16:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-25 20:21 [parisc-linux] Program counter from sigcontext, constructors Boehm, Hans
2003-04-25 21:37 ` John David Anglin
2003-04-26 16:08   ` Carlos O'Donell [this message]
2003-04-26 17:33     ` John David Anglin
2003-04-26 21:24       ` Carlos O'Donell
2003-04-27  0:28         ` John David Anglin

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=20030426160829.GE8269@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=hans_boehm@hp.com \
    --cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.