From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Michael Snyder <msnyder@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] improved error message
Date: Mon, 16 Dec 2002 08:36:00 -0000 [thread overview]
Message-ID: <20021216163625.GB16417@nevyn.them.org> (raw)
In-Reply-To: <3DFDFE7C.3060100@redhat.com>
On Mon, Dec 16, 2002 at 11:25:32AM -0500, Andrew Cagney wrote:
> >There are like five places in thread-db.c that all give the same
> >error message. This just adds the function name, so you have a
> >chance of figuring out where the error occurred.
> >
> >2002-12-13 Michael Snyder <msnyder@to-limbo.toronto.redhat.com>
> >
> > * thread-db.c (thread_from_lwp): Uniquify error msg.
> > (lwp_from_thread): Ditto.
> > (check_event): Ditto.
> > (find_new_threads_callback): Ditto.
> > (thread_db_pid_to_str): Ditto.
>
> Er, this looks wrong. A normal user visible error message should not
> include references to internal function names. Can you either reword
> the messages or, perhaphs, add a debug mode that displys this additional
> information?
These are essentially internal error messages - none of them should
ever happen. They do now, of course.
IMVHO I like Michael's change; now when people report these error
messages I'll know automatically which one they are. They tend to be
only spontaneously reproducible.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-12-16 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 23:20 Michael Snyder
2002-12-16 8:31 ` Andrew Cagney
2002-12-16 8:36 ` Daniel Jacobowitz [this message]
2002-12-16 8:56 ` Andrew Cagney
2002-12-16 9:01 ` Daniel Jacobowitz
2002-12-16 11:25 ` Andrew Cagney
2002-12-16 8:40 ` Michal Ludvig
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=20021216163625.GB16417@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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