From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Error message uniformity
Date: Mon, 30 Jan 2023 16:36:44 -0700 [thread overview]
Message-ID: <874js7h9wz.fsf@tromey.com> (raw)
In-Reply-To: <c7771b80-427a-5df6-c829-151f066b0df5@simark.ca> (Simon Marchi's message of "Mon, 30 Jan 2023 11:13:37 -0500")
Simon> However, I think it would be worth factoring all of these in a single
Simon> function (e.g. error_no_symbol_table).
It's a little funny because the linespec ones throw a specific exception.
Though I wonder if they all could.
Tom
prev parent reply other threads:[~2023-01-30 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-28 3:11 Tom Tromey
2023-01-30 16:13 ` Simon Marchi
2023-01-30 23:36 ` Tom Tromey [this message]
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=874js7h9wz.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/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).