public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/27667] FAIL: gdb.mi/mi-sym-info.exp: List all functions from debug information only (timeout)
Date: Wed, 31 Mar 2021 13:57:59 +0000 [thread overview]
Message-ID: <bug-27667-4717-CjjvfxBAZd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27667-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27667
--- Comment #23 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #9)
> (In reply to Simon Marchi from comment #8)
> > Hi Tom!
> >
> > If you found these debug prints useful, chances are they'll be useful to
> > others too in the future, so please consider adding them upstream :)
>
> Hi Simon.
>
> That makes sense, I'll see what I can do.
Posted https://sourceware.org/pipermail/gdb-patches/2021-March/177397.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-31 13:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 13:34 [Bug testsuite/27667] New: " vries at gcc dot gnu.org
2021-03-30 13:46 ` [Bug testsuite/27667] " vries at gcc dot gnu.org
2021-03-30 13:54 ` vries at gcc dot gnu.org
2021-03-30 15:04 ` vries at gcc dot gnu.org
2021-03-30 15:11 ` vries at gcc dot gnu.org
2021-03-30 15:22 ` matz at suse dot de
2021-03-30 15:24 ` matz at suse dot de
2021-03-30 15:33 ` vries at gcc dot gnu.org
2021-03-30 15:39 ` simark at simark dot ca
2021-03-30 15:43 ` vries at gcc dot gnu.org
2021-03-30 15:58 ` vries at gcc dot gnu.org
2021-03-30 16:34 ` matz at suse dot de
2021-03-30 20:43 ` vries at gcc dot gnu.org
2021-03-31 7:46 ` vries at gcc dot gnu.org
2021-03-31 9:15 ` mliska at suse dot cz
2021-03-31 9:31 ` vries at gcc dot gnu.org
2021-03-31 9:51 ` vries at gcc dot gnu.org
2021-03-31 10:06 ` vries at gcc dot gnu.org
2021-03-31 10:53 ` vries at gcc dot gnu.org
2021-03-31 10:53 ` vries at gcc dot gnu.org
2021-03-31 10:59 ` vries at gcc dot gnu.org
2021-03-31 12:34 ` vries at gcc dot gnu.org
2021-03-31 13:17 ` cvs-commit at gcc dot gnu.org
2021-03-31 13:57 ` vries at gcc dot gnu.org [this message]
2021-03-31 14:00 ` vries at gcc dot gnu.org
2021-03-31 14:46 ` vries at gcc dot gnu.org
2021-04-01 6:07 ` vries at gcc dot gnu.org
2021-04-01 6:22 ` vries at gcc dot gnu.org
2021-04-01 6:26 ` vries at gcc dot gnu.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-27667-4717-CjjvfxBAZd@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).