This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Debugging 64-bit programs using 32-bit GDB
- From: Pedro Alves <palves at redhat dot com>
- To: Doug Evans <dje at google dot com>
- Cc: Nikita Karetnikov <nikita at karetnikov dot org>, gdb <gdb at sourceware dot org>
- Date: Wed, 24 Jul 2013 17:30:05 +0100
- Subject: Re: Debugging 64-bit programs using 32-bit GDB
- References: <87r4f8oxo3 dot fsf at karetnikov dot org> <51EFE5C0 dot 60706 at redhat dot com> <CADPb22Q-Z19v99FUs-1vMYrMxaq0knQtU_tPkPYcDeNrgY0f6Q at mail dot gmail dot com> <51EFFFD7 dot 4000000 at redhat dot com>
On 07/24/2013 05:24 PM, Pedro Alves wrote:
>> When does the above error get triggered?
>
> Looks like it doesn't.
I realized I might have replied to the wrong question.
I was saying that for 32-bit x86 GDB, that error isn't
triggered, because the code isn't reached.
That error in amd64-linux-nat.c is triggered when you try
to debug a 64-bit process with an x32 (not 32-bit x86) GDB.
--
Pedro Alves