Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: cagney@redhat.com, ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfc/testsuite/mi] use gdb_get_line_number
Date: Wed, 11 Aug 2004 18:08:00 -0000	[thread overview]
Message-ID: <411A609D.3080306@gnu.org> (raw)
In-Reply-To: <41188B2A.nailK7Y1RD9SU@mindspring.com>

> Here is a draft patch for gdb.mi/mi-break.exp to use
> gdb_get_line_number.
> 
> It works, but that's beside the point.  I'm looking for the right style.
> So this is RFC, not RFA.
> 
> Some questions:
> 
> . there are a lot of line_* variables.  how would you like me to name
>   them and manage them?
> 
> . some of the test names have line numbers embedded in them:
> 
>     "insert temp breakpoint at basics.c:15 (callee3)"
> 
>   this is now
> 
>     "insert temp breakpoint at basics.c:$line_callee3 (callee3)"
> 
>   so the name floats around as basics.c changes.  That is, I just
>   did the simple stupid substitution.  What would you really like for
>   test names like this?

Yea, not really. basics.c:callee3 && basics.callee3.prolog?


> + # Locate line numbers in basics.c.
> + set line_callee4        [expr [gdb_get_line_number "callee4 ("]]
> + set line_callee4_plus_2 [expr [gdb_get_line_number "callee4 ("] + 2]

I'm wondering if the latter should be called:

	line_callee4_past_prologue

(that specific name is bad but I think the intent is clear) so it's 
clear that it is past the callee4's prologu.

Andrew



  reply	other threads:[~2004-08-11 18:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10  8:45 Michael Chastain
2004-08-11 18:08 ` Andrew Cagney [this message]
2004-08-11 18:53   ` Michael Chastain
2004-08-11 20:14     ` Andrew Cagney
2004-08-11 22:17       ` Michael Chastain
2004-08-11 23:00         ` Andrew Cagney
2004-08-12 12:03           ` Michael Chastain
2004-08-12 12:12             ` Andrew Cagney
2004-08-12 12:45               ` Michael Chastain
2004-08-11 19:22   ` Michael Chastain

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=411A609D.3080306@gnu.org \
    --to=cagney@gnu.org \
    --cc=cagney@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec.gnu@mindspring.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