From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: jan.kratochvil@redhat.com (Jan Kratochvil)
Cc: frederic.riss@gmail.com (Frederic Riss),
pedro@codesourcery.com (Pedro Alves),
gdb-patches@sourceware.org
Subject: Re: [patch 1/3] Clear stale specific locs, not whole bpts [rediff]
Date: Fri, 11 Jun 2010 16:24:00 -0000 [thread overview]
Message-ID: <201006111624.o5BGOegq009123@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20100610203913.GA11204@host0.dyn.jankratochvil.net> from "Jan Kratochvil" at Jun 10, 2010 10:39:13 PM
Jan Kratochvil wrote:
> gdb/testsuite/
> 2010-06-10 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * gdb.base/moribund-step.exp: New.
> +gdb_test_no_output "set non-stop on"
> +
> +if ![runto_main] {
> + return
> +}
This fails on platforms that do not support non-stop mode:
(gdb) set non-stop on^M
(gdb) PASS: gdb.base/moribund-step.exp: set non-stop on
delete breakpoints^M
(gdb) info breakpoints^M
No breakpoints or watchpoints.^M
(gdb) break main^M
Breakpoint 1 at 0x18c: file /home/uweigand/fsf/gdb-head/gdb/testsuite/gdb.base/start.c, line 34.^M
(gdb) run ^M
The target does not support running in non-stop mode.^M
(gdb) FAIL: gdb.base/moribund-step.exp: running to main in runto
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2010-06-11 16:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 20:02 [patch 1/3] Clear stale specific locs, not whole bpts Jan Kratochvil
2010-05-17 21:25 ` [patch 1/3] Clear stale specific locs, not whole bpts [rediff] Jan Kratochvil
2010-05-24 12:18 ` Pedro Alves
2010-06-04 19:19 ` Jan Kratochvil
2010-06-07 11:50 ` Pedro Alves
2010-06-07 13:40 ` Jan Kratochvil
2010-06-10 14:09 ` Frederic Riss
2010-06-10 20:39 ` Jan Kratochvil
2010-06-11 7:58 ` Frederic Riss
2010-06-11 13:00 ` Jan Kratochvil
2010-06-11 10:50 ` Pedro Alves
2010-06-11 16:24 ` Ulrich Weigand [this message]
2010-06-11 18:34 ` Jan Kratochvil
2010-06-11 21:51 ` Ulrich Weigand
2010-06-11 21:59 ` 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=201006111624.o5BGOegq009123@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=frederic.riss@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pedro@codesourcery.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