From: Simon Marchi <simon.marchi@polymtl.ca>
To: Andrew Burgess <aburgess@redhat.com>,
Simon Marchi <simon.marchi@efficios.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH v2] gdb/dwarf: dump cooked index contents in cooked_index_functions::dump
Date: Tue, 31 Jan 2023 10:49:10 -0500 [thread overview]
Message-ID: <92a28fac-9d20-f0be-fd7e-b9ad8683c615@polymtl.ca> (raw)
In-Reply-To: <877cx3uki5.fsf@redhat.com>
> I think this would be a good improvement. Especially the "No debugging
> symbols found..." message now being printed, is, I think, a good thing.
Although I agree with you, given Tom's answer, I will go with the simple
nullptr check. Hopefully we can being back the "No debugging symbols
found" message at some later point.
Simon
next prev parent reply other threads:[~2023-01-31 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 16:03 Simon Marchi
2023-01-30 16:08 ` Simon Marchi
2023-01-30 19:07 ` Tom Tromey
2023-01-30 20:08 ` Simon Marchi
2023-01-30 21:35 ` Andrew Burgess
2023-01-31 3:06 ` Simon Marchi
2023-01-31 9:21 ` Andrew Burgess
2023-01-31 15:49 ` Simon Marchi [this message]
2023-01-31 17:27 ` Tom Tromey
2023-01-31 14:19 ` Tom Tromey
2023-01-31 15:35 ` Simon Marchi
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=92a28fac-9d20-f0be-fd7e-b9ad8683c615@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).