Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Camm Maguire <camm@maguirefamily.org>,
	debian-mips@lists.debian.org,
	Frederick Isaac <freddyisaac@gmail.com>,
	gcl-devel@gnu.org, linux-mips <linux-mips@linux-mips.org>
Subject: Re: gdb for mips64
Date: Tue, 26 Oct 2010 10:19:37 -0700	[thread overview]
Message-ID: <4CC70DA9.6000906@caviumnetworks.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1010261323080.15889@eddie.linux-mips.org>

On 10/26/2010 05:47 AM, Maciej W. Rozycki wrote:
> On Mon, 25 Oct 2010, David Daney wrote:
>
>> I don't think a 32-bit gdb can debug 64-bit processes :-(.
>
>   And it should (assuming ptrace(2) gets things right) -- if what you say
> is true, then it's a bug rather than a deliberate design decision.  To add
> some irony, MIPS GDB is always 64-bit internally.
>
>>> (gdb) r
>>> Starting program: /home/camm/gcl-2.6.8pre/unixport/saved_pre_gcl
>>> /home/wingsun/develop/build/gdb/gdb-6.8/gdb/mips-tdep.c:603: internal-error:
>>> bad register size
>>> A problem internal to GDB has been detected,
>>> further debugging may prove unreliable.
>
>   Try a newer version though -- GDB 7.2 has been out for a (short) while
> now.  You're missing 2.5 years of development.  If still unsuccessful with
> a pristine release from ftp.gnu.org, then file a bug report at
> http://sourceware.org/gdb/bugs/.
>

After more though, I think you may have to configure with 
--enable-64-bit-bfd for a 32-bit gdb to work on 64-bit processes. 
Although I have not actually tested that.  In the past, I have just 
built a native 64-bit gdb.

David Daney

  reply	other threads:[~2010-10-26 17:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1OwbkA-0006gv-Bi@localhost.m.enhanced.com>
     [not found] ` <4C93993E.7030008@caviumnetworks.com>
     [not found]   ` <8762y49k1k.fsf@maguirefamily.org>
     [not found]     ` <4C93D86D.5090201@caviumnetworks.com>
     [not found]       ` <87fwx4dwu5.fsf@maguirefamily.org>
     [not found]         ` <4C97D9A1.7050102@caviumnetworks.com>
     [not found]           ` <87lj6te9t1.fsf@maguirefamily.org>
     [not found]             ` <4C9A8BC9.1020605@caviumnetworks.com>
     [not found]               ` <4C9A9699.6080908@caviumnetworks.com>
     [not found]                 ` <87pqvbs7oa.fsf@maguirefamily.org>
     [not found]                   ` <4CB88D2C.8020900@caviumnetworks.com>
     [not found]                     ` <87r5fksxby.fsf_-_@maguirefamily.org>
2010-10-20 16:38                       ` recent SIGBUS/SIGSEGV mips kernel bug David Daney
2010-10-20 21:31                         ` Camm Maguire
2010-10-21 16:19                           ` David Daney
2010-10-21 16:32                             ` Camm Maguire
2010-10-21 17:29                             ` David Daney
2010-10-21 19:07                               ` Camm Maguire
2010-10-25 20:11                               ` Camm Maguire
2010-10-25 21:32                               ` gdb for mips64 Camm Maguire
2010-10-25 21:45                                 ` David Daney
2010-10-26 12:47                                   ` Maciej W. Rozycki
2010-10-26 17:19                                     ` David Daney [this message]
2010-11-01 16:24                                       ` mips and ADDR_NO_RANDOMIZE Camm Maguire
2010-11-01 18:06                                         ` David Daney
2010-11-01 18:24                                           ` Camm Maguire
2010-10-26 14:47                                   ` gdb for mips64 Camm Maguire
2010-10-26 20:12                                     ` [Gcl-devel] " Camm Maguire
2010-10-28 10:50                                       ` Maciej W. Rozycki
2010-10-28 21:28                                         ` Camm Maguire
2010-10-29  7:47                                           ` Maciej W. Rozycki
2010-10-29 15:52                                             ` Camm Maguire
2010-10-30 12:39                                               ` Maciej W. Rozycki

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=4CC70DA9.6000906@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=camm@maguirefamily.org \
    --cc=debian-mips@lists.debian.org \
    --cc=freddyisaac@gmail.com \
    --cc=gcl-devel@gnu.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.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