public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sourceware.org
Subject: Re: [RFC] The never ending 32-bit vs. 64-bit blues
Date: Mon, 07 Nov 2005 22:59:00 -0000	[thread overview]
Message-ID: <20051107225937.GA29930@nevyn.them.org> (raw)
In-Reply-To: <200511072245.jA7MjnIL005849@elgar.sibelius.xs4all.nl>

On Mon, Nov 07, 2005 at 11:45:49PM +0100, Mark Kettenis wrote:
> In the past we have had a lot of bug reports from people trying to
> debug 64-bit programs with a native 32-bit gdb.  As far as I know we
> don't support any native configuration that allows this.  I've never
> quite managed to come up with a satisfactory solution to deal with
> this.  Here's an attempt to deal with it by making configure complain.
> 
> Any opinions about this?

For the situation as you've stated it, I don't agree.  Not only did
Richard post some PPC Linux patches to make this work, I'll have
patches for it for MIPS Linux shortly; I've done all the kernel bits
already and most of the testing.

The patch as you've posted it, however, isn't really very useful for
that goal.  But it does seem useful for another.  When you build a
32-bit PowerPC debugger you should be configuring it for powerpc-linux;
if you configure it for powerpc64-linux but use -m32, you're likely to
get pretty surprising results.  So I have no problem with the patch
itself :-)

-- 
Daniel Jacobowitz
CodeSourcery, LLC

      parent reply	other threads:[~2005-11-07 22:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-07 22:45 Mark Kettenis
2005-11-07 22:50 ` Jim Ingham
2005-11-07 22:52 ` David Lecomber
2005-11-07 22:59 ` Daniel Jacobowitz [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=20051107225937.GA29930@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).