From: Michael Snyder <msnyder@redhat.com>
To: m.m.kettenis@chello.nl
Cc: gdb-patches@sources.redhat.com, drow@mvista.com,
ac131313@cygnus.com, thorpej@wasabisystems.com
Subject: Re: [PATCH/RFA] Don't gdbarch_init for core files
Date: Fri, 17 May 2002 10:54:00 -0000 [thread overview]
Message-ID: <3CE5408C.A2F48EC1@redhat.com> (raw)
In-Reply-To: <20020517135849.ZGDH1268.amsfep15-int.chello.nl@[127.0.0.1]>
m.m.kettenis@chello.nl wrote:
>
> Michael Snyder wrote:
> > > > 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! ;-)
>
> Ah, but in that case, why not call set_gdbarch_from_file() only when exec_bfd is NULL? As in:
>
> if (!exec_bfd)
> set_gdbarch_from_file (core_bfd);
>
> I tested this, and it seems to solve the problems for me when testing my pending i386 multi-arch patches on Linux.
I cannot immediately think of any objections to this.
Michael
next prev parent reply other threads:[~2002-05-17 17:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2002-05-16 16:24 ` Michael Snyder
2002-05-16 17:33 ` Andrew Cagney
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=3CE5408C.A2F48EC1@redhat.com \
--to=msnyder@redhat.com \
--cc=ac131313@cygnus.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=m.m.kettenis@chello.nl \
--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