From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: [x86_64-linux] ptrace (PT_STEP) causes 2 instruction step???
Date: Thu, 23 Nov 2006 16:13:00 -0000 [thread overview]
Message-ID: <20061123161319.GA11623@nevyn.them.org> (raw)
In-Reply-To: <20061123042227.GA22601@adacore.com>
On Wed, Nov 22, 2006 at 08:22:27PM -0800, Joel Brobecker wrote:
> I searched the internet a bit, and apparently this type of error
> has happened a while ago. Unfortunately, I lost the link, but the
> reports were saying that the problem they saw only occured in a
> very specific case, which is not the case here...
That was over syscalls, I think.
> Has anyone seen this before? Any clue? Surprisingly, all our
> x86_64-linux machines started showing these symptoms on the same
> day. All except one, which keeps working fine.
Like Mark, I'm suspicious of updates. I've never seen this behavior
before.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-11-23 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 4:22 Joel Brobecker
2006-11-23 8:35 ` Mark Kettenis
2006-11-24 17:54 ` Joel Brobecker
2006-11-23 16:13 ` Daniel Jacobowitz [this message]
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=20061123161319.GA11623@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb@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