Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: "Boehm, Hans" <hans_boehm@hp.com>,
	"'parisc-linux@lists.parisc-linux.org'"
	<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Program counter from sigcontext, constructurs and -fPIC
Date: Tue, 29 Apr 2003 20:31:06 -0400	[thread overview]
Message-ID: <20030430003106.GC12492@systemhalted> (raw)
In-Reply-To: <20030429221357.GD17313@dsl2.external.hp.com>

g,

> no - he's using:
> grundler@debian:~$ uname -a
> Linux debian 2.4.20-pa28 #39 Wed Mar 12 19:24:25 PST 2003 parisc unknown
> unknown GNU/Linux

Perfect.
 
> It's possible the kernel-headers he's using aren't clean.
> Just in case, can you tell me which ones he should be using?

/usr/inlcude/asm/sigcontext.h should define it to be:

/* We will add more stuff here as it becomes necessary, until we know
   it works. */
struct sigcontext {
        unsigned long sc_flags;
        unsigned long sc_gr[32]; /* PSW in sc_gr[0] */
        unsigned long long sc_fr[32]; /* FIXME, do we need other state info? */
        unsigned long sc_iasq[2];
        unsigned long sc_iaoq[2];
        unsigned long sc_sar; /* cr11 */
};

Which is used to define an identical mcontext.

> ii  libc6          2.3.1-16       GNU C Library: Shared libraries and Timezone
> ii  libc6-dev      2.3.1-16       GNU C Library: Development Libraries and Hea

Perfect.

> I'm ok with updating to -17 if you promise it won't do evil things
> to my box. ;^)

Don't touch -17, the _Unwind_Find_FDE code broke and it's doing damage
to things like 'vi' ... *sigh* I haven't even looked into this (looks
like gcc/glibc clashes again).

c.

  reply	other threads:[~2003-04-30  0:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-29 21:17 [parisc-linux] Program counter from sigcontext, constructurs and -fPIC Boehm, Hans
2003-04-29 21:30 ` Carlos O'Donell
2003-04-29 22:13   ` Grant Grundler
2003-04-30  0:31     ` Carlos O'Donell [this message]
2003-04-30  5:18       ` Grant Grundler
2003-04-30  7:15       ` Joel Soete
2003-04-30 18:12         ` Carlos O'Donell
2003-05-03 20:48           ` Joel Soete
2003-05-05  6:08             ` Joel Soete
2003-05-01  4:09 ` Grant Grundler
  -- strict thread matches above, loose matches on Subject: below --
2003-04-30  0:52 Boehm, Hans
2003-04-25 19:40 Boehm, Hans
2003-04-25 20:52 ` Carlos O'Donell
2003-04-25 17:46 Boehm, Hans
2003-04-25 18:54 ` Carlos O'Donell

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=20030430003106.GC12492@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=grundler@parisc-linux.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox