Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@kealia.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFC] Fix break.exp optimization related failure
Date: Sat, 27 Sep 2003 00:31:00 -0000	[thread overview]
Message-ID: <yf2n0cr5axd.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <1030927002610.ZM28054@localhost.localdomain> (Kevin Buettner's message of "Fri, 26 Sep 2003 17:26:11 -0700")

On Fri, 26 Sep 2003 17:26:11 -0700, Kevin Buettner <kevinb@redhat.com> said:

> The changes to break.exp look significant, but are only line number
> changes.  I added exactly 20 lines to break.c, so most line numbers
> increase by 20.  Those that don't are either before or within the
> range of lines affected by my patch.

Could you use gdb_get_line_number to get rid of the sensitivity on
line numbers?

David Carlton
carlton@kealia.com


  reply	other threads:[~2003-09-27  0:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-27  0:26 Kevin Buettner
2003-09-27  0:31 ` David Carlton [this message]
2003-09-27  1:05   ` Kevin Buettner
2003-09-27 15:46 ` Andrew Cagney
2003-09-27 19:15 Michael Elizabeth Chastain
2003-09-27 19:30 ` Mark Kettenis

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=yf2n0cr5axd.fsf@hawaii.kealia.com \
    --to=carlton@kealia.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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