Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: fnf@redhat.com, gdb-patches@sources.redhat.com
Subject: Your patch to list.exp
Date: Mon, 25 Mar 2002 17:11:00 -0000	[thread overview]
Message-ID: <20020325201108.A28503@nevyn.them.org> (raw)

I just saw this on gdb-cvs.  Was it ever on gdb-patches?  I don't recall
seeing it at least.

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.

revision 1.5
date: 2002/03/26 00:36:07;  author: fnf;  state: Exp;  lines: +2 -7
        2002-03-25  Fred Fish  <fnf@redhat.com>
        * gdb.base/list.exp: This test works on remote targets so remove
        the short circuit for remote targets.  Update copyright.
----------------------------
revision 1.4
date: 2002/02/14 06:25:18;  author: drow;  state: Exp;  lines: +1 -1
2002-02-14  Daniel Jacobowitz  <drow@mvista.com>

        * gdb.base/a2-run.exp: Check for a remote target properly.
        * gdb.base/annota1.exp: Likewise.
        * gdb.base/list.exp: Likewise.
        * gdb.base/reread.exp: Likewise.
        * gdb.base/scope.exp: Likewise.
        * gdb.base/shlib-call.exp: Likewise.
        * gdb.base/term.exp: Likewise.
        * gdb.c++/annota2.exp: Likewise.

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


             reply	other threads:[~2002-03-26  1:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-25 17:11 Daniel Jacobowitz [this message]
2002-03-25 20:12 ` Fred Fish
2002-03-25 20:30   ` Daniel Jacobowitz
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=20020325201108.A28503@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