Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Nitin Gupta <ngupta@mvista.com>
Cc: gdb@sourceware.org
Subject: Re: [PATCH]: Clarify the warning displayed when you debug a core file  for the wrong architecture.
Date: Tue, 28 Nov 2006 19:01:00 -0000	[thread overview]
Message-ID: <m3slg3tmyh.fsf@codesourcery.com> (raw)
In-Reply-To: <456B8B19.8050403@mvista.com> (Nitin Gupta's message of "Mon, 27 Nov 2006 17:04:25 -0800")


Nitin Gupta <ngupta@mvista.com> writes:
> Pushing one of the old patches from Daniel into FSF.
>
> 2002-08-30  Daniel Jacobowitz  <drow@mvista.com>
>
>        * corelow.c (get_core_register_section): Clarify warning.
>
> Index: gdb-6.3.90_20051109/gdb/corelow.c
> ===================================================================
> --- gdb-6.3.90_20051109.orig/gdb/corelow.c      2005-07-04
> 13:29:10.000000000 +0000
> +++ gdb-6.3.90_20051109/gdb/corelow.c   2005-11-09 23:23:54.000000000 +0000
> @@ -462,7 +462,10 @@
>   if (! section)
>     {
>       if (required)
> +      {
>        warning (_("Couldn't find %s registers in core file."), human_name);
> +       warning (_("Core file may be for a different architecture.\n"));
> +      }
>       return;
>     }

I don't object to this patch, but I wonder if there isn't a better
place to do the check, where we could issue a more informative
message.

Does this warning ever come about when the core file is *not* of a
different architecture?  I'd assume not, since the caller indicated
that the section in question is required.

(Sorry if this patch has been discussed before --- I couldn't find the
thread in the archives.)


  reply	other threads:[~2006-11-28 19:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28  1:04 Nitin Gupta
2006-11-28 19:01 ` Jim Blandy [this message]
2006-11-28 19:51   ` Mark Kettenis
2006-11-28 19:58     ` Jim Blandy
2006-11-29  0:04       ` Mark Kettenis
2006-12-06 17:50         ` Nitin Gupta

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=m3slg3tmyh.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=gdb@sourceware.org \
    --cc=ngupta@mvista.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