From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: vladimir@codesourcery.com (Vladimir Prus)
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Stop infrun from tracking breakpoint insertion status.
Date: Mon, 26 Nov 2007 15:25:00 -0000 [thread overview]
Message-ID: <200711261524.lAQFOu2E025275@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <200711221821.02413.vladimir@codesourcery.com> from "Vladimir Prus" at Nov 22, 2007 06:21:01 PM
Vladimir Prus wrote:
> On Thursday 22 November 2007 03:49:22 you wrote:
> > Hmmm, if it helps, I could run a test on AIX, which does use
> > TARGET_WAITKIND_LOADED.
>
> That would surely help in convincing ourself the patch don't
> break anything.
I did a test run on AIX now, and unfortunately it did break.
I didn't look into the failure in detail, but apparently it
is unrelated to TARGET_WAITKIND_LOADED, but rather to software
single-step support:
rios2 10$ ./gdb testsuite/gdb.base/all-types
GNU gdb 6.7.50.20071126-cvs
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc-ibm-aix5.3.0.0"...
Setting up the environment for debugging gdb.
Function "internal_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) [answered N; input not from terminal]
Function "info_command" not defined.
Make breakpoint pending on future shared library load? (y or [n]) [answered N; input not from terminal]
/c1dje/c1dje/gdb-head-build/gdb/.gdbinit:8: Error in sourced command file:
No breakpoint number 0.
(gdb) start
Breakpoint 1 at 0x1000037c: file /c1dje/c1dje/gdb-head/gdb/testsuite/gdb.base/all-types.c, line 35.
Starting program: /c1dje/c1dje/gdb-head-build/gdb/testsuite/gdb.base/all-types
main () at /c1dje/c1dje/gdb-head/gdb/testsuite/gdb.base/all-types.c:35
35 dummy();
(gdb) n
Program exited normally.
(gdb) start
Breakpoint 2 at 0x1000037c: file /c1dje/c1dje/gdb-head/gdb/testsuite/gdb.base/all-types.c, line 35.
Starting program: /c1dje/c1dje/gdb-head-build/gdb/testsuite/gdb.base/all-types
main () at /c1dje/c1dje/gdb-head/gdb/testsuite/gdb.base/all-types.c:35
35 dummy();
(gdb) n
/c1dje/c1dje/gdb-head/gdb/breakpoint.c:8140: internal-error: insert_single_step_breakpoint: Assertion `single_step_breakpoints[1] == NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Note how not only single-step does not work, but it appears to leave
its data structures in an inconsisten state to that a subsequent attempt
to use single-step breakpoints triggers an internal error ...
Can you have a look?
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:[~2007-11-26 15:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-18 11:41 Vladimir Prus
2007-11-19 11:39 ` Ulrich Weigand
2007-11-19 17:00 ` Vladimir Prus
2007-11-20 20:48 ` Vladimir Prus
2007-11-22 0:49 ` Ulrich Weigand
2007-11-22 15:21 ` Vladimir Prus
2007-11-26 15:25 ` Ulrich Weigand [this message]
2007-11-27 17:49 ` Vladimir Prus
2007-11-27 18:14 ` Ulrich Weigand
2007-11-28 12:50 ` Vladimir Prus
2007-11-27 18:55 ` Vladimir Prus
2007-11-28 22:24 ` Ulrich Weigand
2007-11-29 18:46 ` Vladimir Prus
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=200711261524.lAQFOu2E025275@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@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