Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stephane Carrez <stcarrez@nerim.fr>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Fix testsuite/gdb.base/break.exp when test compiled with -DPROTOTYPES
Date: Mon, 24 Feb 2003 21:46:00 -0000	[thread overview]
Message-ID: <3E5A92C7.4070205@nerim.fr> (raw)
In-Reply-To: <15962.37096.719113.658720@localhost.redhat.com>

Hi Elena,

Elena Zannoni wrote:

> Stephane Carrez writes:
>  > Hi!
>  > 
>  > In the gdb.base/break.c test, the function marker4() is defined at line 46 when
>  > the test is compiled with -DPROTOTYPES and at line 51 otherwise.  The break.exp
>  > test only check for line 51.
>  > 
>  > This patch adds the missing regexp for marker4 at line 46.
>  > (tested with make check for m6811-elf; break.exp passes completely)
>  > 
>  > Can you approve it?
>  > 
> 
> Could this be fixed by adding a comment to the lines in question,
> use gdb_get_line_number, and use that in the test? 
> 


It's not good because marker4() is defined at 2 different lines.

If we use gdb_get_line_number() it will always find the first match which is at 46

and the test will fail for targets that don't compile their tests with -DPROTOTYPES.


	Stephane



  reply	other threads:[~2003-02-24 21:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 21:19 Stephane Carrez
2003-02-24 21:34 ` Elena Zannoni
2003-02-24 21:46   ` Stephane Carrez [this message]
2003-02-24 23:34     ` Jason Molenda
2003-04-04 20:09 ` Stephane Carrez
2003-04-04 20:41 Michael Elizabeth Chastain
2003-04-04 21:31 ` Stephane Carrez
2003-04-04 22:29   ` Daniel Jacobowitz
2003-04-05 10:46     ` Stephane Carrez
2003-04-05 13:20       ` Andrew Cagney

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=3E5A92C7.4070205@nerim.fr \
    --to=stcarrez@nerim.fr \
    --cc=ezannoni@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