From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Cc: Aleksandar Ristovski <aristovski@qnx.com>
Subject: [commit] testsuite: Fix break-inline.exp with gdbserver
Date: Sun, 19 Feb 2012 16:42:00 -0000 [thread overview]
Message-ID: <20120219131048.GA16245@host2.jankratochvil.net> (raw)
In-Reply-To: <4F3C0796.1080002@qnx.com>
On Wed, 15 Feb 2012 20:29:26 +0100, Aleksandar Ristovski wrote:
> On 12-02-15 11:09 AM, Tom Tromey wrote:
> > Aleksandar> 2012-02-14 Aleksandar Ristovski<aristovski@qnx.com>
> >
> > Aleksandar> * gdb.base/break-inline.exp: New file.
> > Aleksandar> * gdb.base/break-inline.c: New file.
[...]
> Committed, thank you.
with
http://sourceware.org/gdb/wiki/TestingGDB#Testing_gdbserver_in_a_native_configuration
+ERROR: gdbserver does not support start without extended-remote
Checked in.
The former internal error is then reproducible even with gdbserver.
(Plus I fixed the parantheses which had no effect before, forgot it in
ChangeLog.)
Thanks,
Jan
http://sourceware.org/ml/gdb-cvs/2012-02/msg00109.html
--- src/gdb/testsuite/ChangeLog 2012/02/17 19:24:26 1.3078
+++ src/gdb/testsuite/ChangeLog 2012/02/19 13:05:27 1.3079
@@ -1,3 +1,9 @@
+2012-02-19 Jan Kratochvil <jan.kratochvil@redhat.com>
+
+ Fix for gdbserver non-extended mode.
+ * gdb.base/break-inline.exp (start): Replace "start" by gdb_breakpoint
+ and gdb_run_cmd.
+
2012-02-17 Tom Tromey <tromey@redhat.com>
* gdb.python/py-events.py (exit_handler): Add test for 'dir'.
--- src/gdb/testsuite/gdb.base/break-inline.exp 2012/02/15 19:27:59 1.1
+++ src/gdb/testsuite/gdb.base/break-inline.exp 2012/02/19 13:05:28 1.2
@@ -18,7 +18,9 @@
return -1
}
-gdb_test "start" "Temporary breakpoint.*foo().*"
+gdb_breakpoint "main" "temporary"
+gdb_run_cmd
+gdb_test "" "Temporary breakpoint.*foo\\(\\).*"
# Now test 'break' with no arguments.
gdb_test "break" "Breakpoint.*"
next prev parent reply other threads:[~2012-02-19 13:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 18:03 [patch] Assert when 'break' with no arguments Aleksandar Ristovski
2012-02-14 18:53 ` Aleksandar Ristovski
2012-02-14 18:06 ` Aleksandar Ristovski
2012-02-14 19:23 ` Joel Brobecker
2012-02-14 20:09 ` Aleksandar Ristovski
2012-02-14 20:18 ` Alfred M. Szmidt
2012-02-14 22:37 ` Aleksandar Ristovski
2012-02-15 17:15 ` Tom Tromey
2012-02-15 20:06 ` Aleksandar Ristovski
2012-02-19 16:42 ` Jan Kratochvil [this message]
2012-02-24 15:52 ` Pedro Alves
2012-02-24 16:00 ` Aleksandar Ristovski
2012-02-24 16:09 ` Pedro Alves
2012-02-24 16:18 ` Aleksandar Ristovski
2012-02-24 17:16 ` Pedro Alves
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=20120219131048.GA16245@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=aristovski@qnx.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