Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] "continue" after "attach" fails on sparc64-solaris
Date: Fri, 07 Mar 2008 19:12:00 -0000	[thread overview]
Message-ID: <20080307191140.GA368@caradoc.them.org> (raw)
In-Reply-To: <20080307184121.GB3892@adacore.com>

On Fri, Mar 07, 2008 at 10:41:21AM -0800, Joel Brobecker wrote:
> This one is relatively straightforward, I think. I could commit it
> in a week or so unless there are objections, but I am afraid that
> it might be priviledge abuse (and I welcome feedback). Since it's
> been out for review for a while, I'll wait another week before
> checking it in. But do let me know if I'm abusing my priviledges.

If anything I think you're underabusing them - we asked you to be a
global maintainer because we trusted your judgement :-)

> > I fixed the problem by implementing a suggestion to use the AT_BASE
> > attributed, but as it turns out, this was only good enough for sparc32.
> > As far as I can tell, the auxilliary data obtained when running a 64bit
> > app looks screwed. So we still have the same problem on sparc64.

This was what threw me off an immediate reply.  I doubt the kernel's
got a bug like this, since Solaris tools use the auxv data.  So we
must have an error when reading it.  Maybe the format is different
than we expect (32-bit vs 64-bit fields)?

Otherwise the patch looks fine.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-03-07 19:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01 18:13 Joel Brobecker
2008-03-07 18:42 ` Joel Brobecker
2008-03-07 19:12   ` Daniel Jacobowitz [this message]
2008-03-07 19:40     ` Joel Brobecker
2008-03-07 22:17       ` Joel Brobecker

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=20080307191140.GA368@caradoc.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --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