Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: Jason R Thorpe <thorpej@wasabisystems.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Don't complain about unknown OSABI
Date: Sun, 18 Aug 2002 11:01:00 -0000	[thread overview]
Message-ID: <3D5FE0DA.7000104@ges.redhat.com> (raw)
In-Reply-To: <3D5FC00D.50001@ges.redhat.com>

> Hello,
> 
> The attached patch removes the warning message that is printed when the OSABI is unknown (all the sniffers failed).
> 
> When debugging an embedded executable, there is no OSABI info.  Hence I don't think the warning should be issued.  This can be seen when debugging a GCC created, mips-elf executable.
> 
> thoughts?

All positive, I've checked it in.

Andrew



      parent reply	other threads:[~2002-08-18 18:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-18  8:41 Andrew Cagney
2002-08-18  8:49 ` Daniel Jacobowitz
2002-08-18  8:54   ` Jason R Thorpe
2002-08-18  9:42   ` Andrew Cagney
2002-08-19  9:15     ` Daniel Jacobowitz
2002-08-19 16:03       ` Andrew Cagney
2002-08-19 16:15         ` Jason R Thorpe
2002-08-19 18:55         ` Daniel Jacobowitz
2002-08-20  9:03           ` Andrew Cagney
2002-08-20  9:11             ` Daniel Jacobowitz
2002-08-21 10:04               ` Andrew Cagney
2002-08-21 10:08                 ` Daniel Jacobowitz
2002-08-21 10:11                   ` Jason R Thorpe
2002-08-21 13:26                     ` Andrew Cagney
2002-08-21 13:38                       ` Daniel Jacobowitz
2002-08-23  6:07                       ` Richard Earnshaw
2002-08-20  9:22             ` Jason R Thorpe
2002-08-20  9:25               ` Jason R Thorpe
2002-08-18  8:51 ` Jason R Thorpe
2002-08-18  8:52 ` Elena Zannoni
2002-08-18 11:01 ` Andrew Cagney [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=3D5FE0DA.7000104@ges.redhat.com \
    --to=ac131313@ges.redhat.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