public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/12074] multi-inferior internal error
Date: Wed, 15 Feb 2012 19:23:00 -0000 [thread overview]
Message-ID: <bug-12074-4717-ChW6bXsatN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12074-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12074
Tom Tromey <tromey at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-02-15
CC| |tromey at redhat dot com
Ever Confirmed|0 |1
--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2012-02-15 19:21:07 UTC ---
This worked in 7.2, failed in 7.3 and 7.4, and works again on HEAD.
I am reluctant to close it because even on HEAD it prints:
(gdb) inferior 2
[Switching to inferior 2 [<null>] (<noexec>)]
(gdb) file sleep
warning: core file may not match specified executable file.
... but this inferior has nothing to do with the core file, presumably.
(Actually I am not 100% sure how this is supposed to work.)
Also, given the history of this bug we should have a test case for it.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next parent reply other threads:[~2012-02-15 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12074-4717@http.sourceware.org/bugzilla/>
2012-02-15 19:23 ` tromey at redhat dot com [this message]
2012-04-11 15:03 ` palves at redhat dot com
2015-01-17 20:47 ` jan.kratochvil at redhat dot com
2015-01-22 20:03 ` cvs-commit at gcc dot gnu.org
2022-06-13 21:35 ` tromey at sourceware dot org
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=bug-12074-4717-ChW6bXsatN@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).