From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: tromey@redhat.com (Tom Tromey)
Cc: pedro@codesourcery.com (Pedro Alves), gdb-patches@sourceware.org
Subject: Re: [3/3] RFC: fix PR mi/8444
Date: Fri, 25 Nov 2011 16:08:00 -0000 [thread overview]
Message-ID: <201111251608.pAPG81oE002175@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <m31usz3la9.fsf@fleche.redhat.com> from "Tom Tromey" at Nov 22, 2011 02:22:06 PM
Tom Tromey wrote:
> * gdb.mi/mi-solib.exp: New file.
> +mi_expect_stop solib-event .* .* .* .* .* "check for solib event"
This causes spurious failures for me, since that routine expects
output in this form:
mi_expect_stop: expecting: \*stopped,reason="solib-event",frame={addr="0x[0-9A-Fa-f]+",func=".*",args=\[.*\],file="[^ ]*.*",fullname="(/[^\n]*/|\\\\[^\\]+\\[^\n]+\\|\\[^\\][^\n]*\\|[a-zA-Z]:[^\n]*\\).*",line=".*"}.*,thread-id="[0-9]+",stopped-threads=[^ ]*
but we actually get
*stopped,reason="solib-event",frame={addr="0x7dfef93c",func="_dl_debug_state",args=[],from="/lib/ld.so.1"},thread-id="1",stopped-threads="all",core="4"
The difference is that we only see a "from=" instead of "file="/"fullname="/"line=" as the PC is in a system library, and I don't have debug info installed for those ...
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:[~2011-11-25 16:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 20:28 Tom Tromey
2011-11-16 21:31 ` Pedro Alves
2011-11-17 16:41 ` Tom Tromey
2011-11-22 14:55 ` Pedro Alves
2011-11-22 21:22 ` Tom Tromey
2011-11-25 16:08 ` Ulrich Weigand [this message]
2011-12-02 1:18 ` [patch] testsuite: Fix mi-solib.exp without debuginfos [Re: [3/3] RFC: fix PR mi/8444] Jan Kratochvil
2011-12-02 16:17 ` Tom Tromey
2011-12-02 22:36 ` [commit] " Jan Kratochvil
2011-12-09 21:26 ` Tom Tromey
2011-12-09 21:54 ` Jan Kratochvil
2011-12-09 21:56 ` Tom Tromey
2011-11-17 4:03 ` [3/3] RFC: fix PR mi/8444 Eli Zaretskii
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=201111251608.pAPG81oE002175@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=tromey@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