From: Michael Snyder <msnyder@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Jason R Thorpe <thorpej@wasabisystems.com>,
Andrew Cagney <ac131313@cygnus.com>,
gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFA] Don't gdbarch_init for core files
Date: Thu, 16 May 2002 16:24:00 -0000 [thread overview]
Message-ID: <3CE43C83.BC71967A@redhat.com> (raw)
In-Reply-To: <20020512034536.GA25145@nevyn.them.org>
Daniel Jacobowitz wrote:
>
> On Sat, May 11, 2002 at 08:30:35PM -0700, Jason R Thorpe wrote:
> > On Sat, May 11, 2002 at 10:48:13PM -0400, Andrew Cagney wrote:
> >
> > > is [almost] no different to deleting the call - GDB isn't yet built with
> > > multiple architectures so the two architectures will always be identical.
> > >
> > > Looking at the date/author of the original patch [and making a wild
> > > guess], I think the original change was related to debugging 32 bit core
> > > files on a SPARC64 system. Michael?
> >
> > Well, I know Solaris dumps a 32-bit core file for a 32-bit binary,
> > and a 64-bit core file for a 64-bit binary.
> >
> > I simply fail to see any reason why you'd want to re-initialize the
> > gdbarch for a core file.
> >
> > I guess I really do need to know why the change was added in the first
> > place (the message with the original patch doesn't describe the problem
> > the patch is trying to solve).
>
> Just a guess - debugging a core file without an original binary?
Bingo! ;-)
next prev parent reply other threads:[~2002-05-16 23:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 18:58 Jason R Thorpe
2002-05-09 20:04 ` Andrew Cagney
2002-05-09 21:21 ` Jason R Thorpe
2002-05-11 19:48 ` Andrew Cagney
2002-05-11 20:30 ` Jason R Thorpe
2002-05-11 20:46 ` Daniel Jacobowitz
2002-05-16 16:24 ` Michael Snyder [this message]
2002-05-16 16:24 ` Michael Snyder
2002-05-16 17:33 ` Andrew Cagney
2002-05-17 6:58 m.m.kettenis
2002-05-17 10:47 ` Jason R Thorpe
2002-05-17 10:59 ` Michael Snyder
2002-05-17 16:06 ` Mark Kettenis
2002-05-17 10:54 ` Michael Snyder
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=3CE43C83.BC71967A@redhat.com \
--to=msnyder@redhat.com \
--cc=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=thorpej@wasabisystems.com \
/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