Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] Allow setting breakpoints on inline functions (PR 10738)
Date: Wed, 30 Nov 2011 20:19:00 -0000	[thread overview]
Message-ID: <20111130201848.GA12763@host2.jankratochvil.net> (raw)
In-Reply-To: <20111129150200.GB3425@redhat.com>

On Tue, 29 Nov 2011 16:02:00 +0100, Gary Benson wrote:
> I'm also interested in feedback about the tests I've
> written, since this is the first time I've worked on the testsuite.

I would prefer definitely a copy in gdb.dwarf2/ .  gdb.opt/ I find a bad idea
as it breaks too much across GCC changes.  just gcc -S -dA is probably OK.

If there is gdb.dwarf2/ then I would even drop the gdb.opt/ one.  Not sure if
it makes sense for non-DWARF targets, the functionality gets tested by the
DWARF targets anyway.


> --- /dev/null
> +++ b/gdb/testsuite/gdb.opt/inline-break.exp
...
> +if { [prepare_for_testing $testfile.exp $testfile $testfile.c \
> +          {debug optimize=-O2 additional_flags=-Winline}] } {

This -Winline is questionable.

You make the .c file compatible even if __GNUC__ is not defined but then you
use GCC-specific -Winline option.  Either just make the testcase whole
GCC-specific or make a fallback if the compilation with -Winline fails try
also non-Winline.  Or maybe just drop that -Winline, there is no -Werror
anyway so it was more just for the testcase development.

As I suggested the gdb.dwarf2/ way this whole -Winline is offtopic then.


> +#
> +# func1 is a static inlined function that is called once.
> +# The result should be a single-location breakpoint.
> +#
> +gdb_test "break func1" \
> +    "Breakpoint.*at.* file .*$testfile\.c, line.*"

As you use "" and not {} you should use \\.c and not \.c .  This way it is the
same as .c .

It is there several times.


> +# func2 is a non-static inlined function that is called once.
> +# The result should be a breakpoint with two locations: the
> +# out-of-line function and the single inlined instance.
> +#
> +gdb_test "break func2" \
> +    "Breakpoint.*at.*func2.*(2 locations).*"

You wanted to use \\( and \\) here.

It is there several times.



Thanks,
Jan


  parent reply	other threads:[~2011-11-30 20:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 15:02 Gary Benson
2011-11-30 17:07 ` Tom Tromey
2011-12-02 13:48   ` Gary Benson
2011-11-30 20:19 ` Jan Kratochvil [this message]
2011-12-01 13:41   ` Gary Benson
2011-12-01 18:53     ` Jan Kratochvil

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=20111130201848.GA12763@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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