Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: fnf@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: Your patch to list.exp
Date: Mon, 25 Mar 2002 20:30:00 -0000	[thread overview]
Message-ID: <20020325233016.A2984@nevyn.them.org> (raw)
In-Reply-To: <200203260412.g2Q4CAw12281@fred.ninemoons.com>

On Mon, Mar 25, 2002 at 09:12:10PM -0700, Fred Fish wrote:
> > I just saw this on gdb-cvs.  Was it ever on gdb-patches?  I don't recall
> > seeing it at least.
> 
> Yes, here is the URL to the original post:
> 
>   http://sources.redhat.com/ml/gdb-patches/2002-01/msg00115.html
> 
> There was also a reply from Kevin Buettner <kevinb@redhat.com> which
> I got in email but which doesn't appear to be in the gdb-patches
> list:

> 
>   I just came across this myself.  I agree with Michael and Fred that the
>   isnative test is bogus.
> 
>   Kevin

Oh yes, I remember now.  Thanks.

> > Is it actually correct if you have debugging information for _start
> > available?  If we connect and are in a known line, presumably we will list
> > there instead.
> 
> Hmm, don't know.  I do know that I originally found this problem with
> an actual remote target for which the patch is OK.

I just verified that the test fails if you have debugging info for
_start.  In light of that, please consider reverting this (and maybe an
informative comment...).

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-03-26  4:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-25 17:11 Daniel Jacobowitz
2002-03-25 20:12 ` Fred Fish
2002-03-25 20:30   ` Daniel Jacobowitz [this message]
2002-03-26  7:04     ` Fernando Nasser
2002-03-26  7:10     ` Fernando Nasser

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=20020325233016.A2984@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=fnf@redhat.com \
    --cc=gdb-patches@sources.redhat.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