Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Rich Coe <Richard.Coe@med.ge.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: gdb x86_64 ERESTARTNOHAND
Date: Tue, 14 Jun 2005 20:21:00 -0000	[thread overview]
Message-ID: <20050614151927.328e1a4c@godzilla> (raw)
In-Reply-To: <20050614143252.GA3288@nevyn.them.org>

when running 32bit apps on a 64bit system, doesn't gdb use
i386-linux-tdep ?

On Tue, 14 Jun 2005 10:32:52 -0400
Daniel Jacobowitz <drow@false.org> wrote:
> On Tue, Jun 14, 2005 at 08:54:25AM -0500, Rich Coe wrote:
> > Run the program below in gdb on x86_64, compiled either -m32 or 64 bit,
> >     stop the execution with control-C
> >     call a function, in this case doNothing(), but sleep(1) works as well
> >     continue
> > gdb passes errno 514 to the program.  514=ERESTARTNOHAND
> > 
> > I see that strace prints out information about ERESTARTNOHAND, so it knows
> > about it.  I was wondering if gdb should know about this, is this an 
> > x86_64 kernel error, or what?
> > 
> > Even though strace knows about ERESTARTNOHAND on i386, and prints it,
> > gdb does not print or cause the program to receive this errno on a 32bit kernel.
> 
> amd64-linux-tdep.c requires a write_pc method, just like the one in
> i386-linux-tdep.c.  Nice catch.
> 
> -- 
> Daniel Jacobowitz
> CodeSourcery, LLC
> 


-- 
Rich Coe		richard.coe@med.ge.com
General Electric Healthcare Technologies
Global Software Platforms, Computer Technology Team


  reply	other threads:[~2005-06-14 20:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14 13:56 Rich Coe
2005-06-14 14:33 ` Daniel Jacobowitz
2005-06-14 20:21   ` Rich Coe [this message]
2005-06-14 20:25     ` 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=20050614151927.328e1a4c@godzilla \
    --to=richard.coe@med.ge.com \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    /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