From: "Douglas Evans" <dje@google.com>
To: gdb@sourceware.org
Subject: Re: dual-arch x86_64/i386 gdb for linux
Date: Fri, 02 Nov 2007 15:34:00 -0000 [thread overview]
Message-ID: <e394668d0711020834t31a2cc58n89ba3ef1519bafa@mail.gmail.com> (raw)
In-Reply-To: <20071102113232.GB16563@caradoc.them.org>
On Nov 2, 2007 4:32 AM, Daniel Jacobowitz <drow@false.org> wrote:
> On Thu, Nov 01, 2007 at 09:37:30PM -0700, Douglas Evans wrote:
> > Hi. Are there any remaining issues for having one gdb binary support
> > both x86_64 and i386 natively on linux? Several things seem to work,
> > and for the things that don't work I'm not sure if it's pilot error or
> > work that is still todo.
>
> Could you elaborate - what doesn't work? I'd expect everything to,
> nowadays. There used to be trouble with libthread_db and
> LinuxThreads, but NPTL's libthread_db should be fine.
It was thread support. I'll try again with NPTL.
Thanks.
prev parent reply other threads:[~2007-11-02 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 4:37 Douglas Evans
2007-11-02 11:32 ` Daniel Jacobowitz
2007-11-02 15:34 ` Douglas Evans [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=e394668d0711020834t31a2cc58n89ba3ef1519bafa@mail.gmail.com \
--to=dje@google.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