public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "dilyan.palauzov at aegee dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/17290] New: typos in gdb/doc/gdbtexinfo.tex, @node Remote Configuration
Date: Mon, 18 Aug 2014 21:21:00 -0000 [thread overview]
Message-ID: <bug-17290-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17290
Bug ID: 17290
Summary: typos in gdb/doc/gdbtexinfo.tex, @node Remote
Configuration
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: cli
Assignee: unassigned at sourceware dot org
Reporter: dilyan.palauzov at aegee dot org
In gdb/doc/gdbtexinfo.tex, @node Remote Configuration, @section Remote
Configuration, please replace lines 18935 and 18990
18932 Record remote serial communications on the named @var{file}. The
18933 default is not to record at all.
18934
18935 @item show remotelogfile.
18936 Show the current setting of the file name on which to record the
18937 serial communications.
18985 @samp{Ctrl-C} is a default. Some system prefers @code{BREAK} which
18986 is high level of serial line for some certain time.
18987 Linux kernel prefers @samp{BREAK-g}, a.k.a Magic SysRq g.
18988 It is @code{BREAK} signal followed by character @code{g}.
18989
18990 @item show interrupt-sequence
18991 Show which of @samp{Ctrl-C}, @code{BREAK} or @code{BREAK-g}
18992 is sent by @value{GDBN} to interrupt the remote program.
18993 @code{BREAK-g} is BREAK signal followed by @code{g} and
with
@item show remotelogfile
(remove terminating dot), and
@item show remote interrupt-sequence
(add 'remote' between 'show' and 'interrupt-sequence')
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-08-18 21:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 21:21 dilyan.palauzov at aegee dot org [this message]
2021-02-27 23:34 ` [Bug cli/17290] " simark at simark dot ca
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=bug-17290-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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).