From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: graces@redhat.com
Cc: msnyder@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: breakpoint error messages
Date: Sat, 24 Aug 2002 02:18:00 -0000 [thread overview]
Message-ID: <3405-Sat24Aug2002121913+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <20020823115315.A13713@tomago.toronto.redhat.com> (message from Grace Sainsbury on Fri, 23 Aug 2002 11:53:15 -0400)
> Date: Fri, 23 Aug 2002 11:53:15 -0400
> From: Grace Sainsbury <graces@redhat.com>
>
> The memory_error is only relevant for memory
> breakpoints, and only insert_breakpoint returns an errno (the hardware
> and catcpoint functions return -1 on error)-- so the call to strerror
> prints the error when it is relevant, and so replaces print_sys_errmsg.
Do we really want to carve in stone the current semi-buggy behavior of
-1 being returned in some of these cases? What if hardware
break/watchpoints and catchpoints code is fixed to return a meaningful
errno?
prev parent reply other threads:[~2002-08-24 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 11:26 Grace Sainsbury
2002-08-22 0:59 ` Eli Zaretskii
2002-08-22 14:24 ` Michael Snyder
2002-08-22 14:38 ` Grace Sainsbury
2002-08-22 15:26 ` Michael Snyder
2002-08-23 9:27 ` Grace Sainsbury
2002-08-23 11:51 ` Michael Snyder
2002-08-24 2:18 ` Eli Zaretskii [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=3405-Sat24Aug2002121913+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=graces@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