From: "Eli Zaretskii" <eliz@elta.co.il>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com, drow@mvista.com
Subject: Re: [rfa/doc/threads] thread breakpoints and system calls
Date: Sun, 26 Oct 2003 17:35:00 -0000 [thread overview]
Message-ID: <1659-Sun26Oct2003193033+0200-eliz@elta.co.il> (raw)
In-Reply-To: <200310261459.h9QExPlc022980@duracef.shout.net> (message from Michael Elizabeth Chastain on Sun, 26 Oct 2003 09:59:25 -0500)
> Date: Sun, 26 Oct 2003 09:59:25 -0500
> From: Michael Elizabeth Chastain <mec@shout.net>
>
> Looking for approval from a thread guy such as Daniel J for content,
> and Eli Z for syntax.
Approved, with one gotcha: the GNU project standards discourage the
use of ``illegal'' for anything other than actions that break the law.
So I would rewrite the following sentence:
> + It is legal behavior for a system call to return early, so @value{GDBN}
> + does not cause your program to behave illegally.
like this:
It is perfectly okay for a system call to return early, so @value{GDBN}
does not cause your problem to behave erratically.
I would also suggest to add that the early return is due to a signal
(SIGTRAP, right?) caused by the breaking breakpoint. This will help
programmers who know that a system call can return early due to a
signal to understand better what's going on.
Thanks.
next prev parent reply other threads:[~2003-10-26 17:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 15:00 Michael Elizabeth Chastain
2003-10-26 17:35 ` Eli Zaretskii [this message]
2003-10-26 17:39 ` Daniel Jacobowitz
2003-10-27 16:12 ` Andrew Cagney
2003-10-27 20:04 ` Eli Zaretskii
2003-10-26 21:35 Michael Elizabeth Chastain
2003-10-27 6:01 ` Eli Zaretskii
2003-10-27 6:04 ` Daniel Jacobowitz
2003-10-27 14:01 Michael Elizabeth Chastain
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=1659-Sun26Oct2003193033+0200-eliz@elta.co.il \
--to=eliz@elta.co.il \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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