From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: gdb-patches@sourceware.org
Subject: Re: [rfa] Handle amd64-linux %orig_rax
Date: Sat, 19 Aug 2006 15:46:00 -0000 [thread overview]
Message-ID: <200608190748.k7J7m5ho005424@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20060819042040.GA14602@nevyn.them.org> (message from Daniel Jacobowitz on Sat, 19 Aug 2006 00:20:40 -0400)
> Date: Sat, 19 Aug 2006 00:20:40 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> x86_64-pc-linux-gnu has an %orig_rax "register", exactly parallel to the
> i386-pc-linux-gnu %orig_eax. It's set to a syscall number to trigger
> system call restarting, and has to be set to -1 when we want to prevent
> restarting. It appears to be in every regard the same as the i386
> version; this copies the i386 handling, and fits it into the existing
> amd64 infrastructure.
>
> Tested on x86_64-pc-linux-gnu; this fixes the interrupt.exp timeouts,
> finally. I've known what this was for ages but never had the patience to
> make the mechanical change before, and someone reported this as a bug on the
> Eclipse CDT list recently.
>
> Does this look OK?
Looks good to me. I vaguely remember orig_rax not being available
through ptrace a couple of years ago, but that probably was before the
first official amd64 Linux distributions came out.
Mark
next prev parent reply other threads:[~2006-08-19 7:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-19 15:34 Daniel Jacobowitz
2006-08-19 15:46 ` Mark Kettenis [this message]
2006-08-19 15:57 ` Daniel Jacobowitz
2006-08-19 16:11 ` [rfa] patch for PR2116 Paul Pluzhnikov
2006-10-09 19:28 ` Daniel Jacobowitz
2006-10-31 18:17 RE:[rfa] Handle amd64-linux %orig_rax Datoda
2006-10-31 18:22 ` [rfa] " Daniel Jacobowitz
2006-10-31 18:40 ` Andi Kleen
2006-10-31 18:49 ` Daniel Jacobowitz
2006-10-31 19:11 ` Andi Kleen
2006-10-31 19:30 ` Daniel Jacobowitz
2006-10-31 19:33 ` Daniel Jacobowitz
2006-10-31 20:10 Datoda
2006-10-31 20:17 ` Andi Kleen
2006-11-01 15:10 Datoda
2006-11-01 15:15 ` Daniel Jacobowitz
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=200608190748.k7J7m5ho005424@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.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