Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: Matthew Wilcox <matthew@wil.cx>, parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] glibc 2.2.3: setjmp/longjmp
Date: Fri, 4 May 2001 23:36:55 +0100	[thread overview]
Message-ID: <20010504233655.K32445@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200105042151.RAA19009@hiauly1.hia.nrc.ca>; from dave@hiauly1.hia.nrc.ca on Fri, May 04, 2001 at 05:51:59PM -0400

On Fri, May 04, 2001 at 05:51:59PM -0400, John David Anglin wrote:
> > On Fri, May 04, 2001 at 05:31:30PM -0400, John David Anglin wrote:
> > > Doesn't look like _setjmp comes back at all.  Put a break on ea18
> > > and start stepping.  It might help to do a static link.
> > 
> > this code is in the dynamic linker :-))
> 
> Can you set a break on main, run to main, set the break in the
> dynamic linker, then continue?

No, though this is probably due more to my lack of skill with gdb than
anything else.

I set a breakpoint on _dl_signal_error ok.
Then inspecting the jmpbuf indicates that it's returning to 4101434f

/proc/<pid>/maps indicates:
0000000041000000-000000004101a000 r-xp 0000000000000000 08:03 1754026    /home/willy/cvs/glibc-build/elf/ld.so

objdump --disassemble shows:

000143e0 <index>:
...
   143f4:       6b d3 3f c1     stw r19,-20(sr0,sp)

which is the middle of nowhere.  Actually, it's right _after_ __longjmp.
clearly it should be returning to 4100ea4c

Going back and setting a breakpoint on _dl_catch_error indicates that the
value being put at ((unsigned long *)c.env)[20] is 0x4101434F, so the jmpbuf
isn't being corrupted...

-- 
Revolutions do not require corporate support.

  reply	other threads:[~2001-05-04 22:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-04 20:05 [parisc-linux] glibc 2.2.3: setjmp/longjmp Matthew Wilcox
2001-05-04 20:18 ` John David Anglin
2001-05-04 20:39   ` Matthew Wilcox
2001-05-04 21:02   ` Matthew Wilcox
2001-05-04 21:31     ` John David Anglin
2001-05-04 21:38       ` Matthew Wilcox
2001-05-04 21:51         ` John David Anglin
2001-05-04 22:36           ` Matthew Wilcox [this message]
2001-05-04 22:56             ` John David Anglin
2001-05-04 22:57           ` Matthew Wilcox
2001-05-05  0:00             ` Matthew Wilcox
2001-05-05  0:49               ` Alan Modra
2001-05-05  1:01                 ` Matthew Wilcox
2001-05-05  1:18                   ` Alan Modra
2001-05-05  1:47                     ` Matthew Wilcox
2001-05-06  6:14         ` Ulrich Drepper
2001-05-06  7:07           ` Grant Grundler
2001-05-06 15:53             ` John David Anglin
2001-05-06 22:13           ` Matthew Wilcox

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=20010504233655.K32445@parcelfarce.linux.theplanet.co.uk \
    --to=matthew@wil.cx \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@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