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 gdb/17281] New: typos in gdb/doc/gdbtexinfo.tex, @node Dynamic Printf Date: Sat, 16 Aug 2014 21:46:00 -0000 [thread overview] Message-ID: <bug-17281-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17281 Bug ID: 17281 Summary: typos in gdb/doc/gdbtexinfo.tex, @node Dynamic Printf Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: dilyan.palauzov at aegee dot org Teach gdb's bugzilla to accept bugs for version 7.8 . In gdb/doc/gdbtexinfo.tex (8d9148cd1cafb), @node Dynamic Printf, @subsection Dynamic Printf please replace line 4820 characters go to the program's output device, so they can recorded in -> characters go to the program's output device, so they can be recorded in 4823 If you are doing remote debugging with a stub or agent, you can also -> If you are doing remote debugging with a stub or an agent, you can also (in @node Set Breaks, @subsection Setting Breakpoints) 3839 executed, given control to the debugger. By default, the program -> executed, is given control to the debugger. By default, the program In @node Dynamic Printf, @subsection Dynamic Printf the styles for set dprintf-style shall be listed as sub-@tables and nested one more level, as reading the current documentaion over info, leaves the impression that the possible styles (gdb, call, etc) are on their own gdb commands. Such nested @tables are e.g. done in in @node Set Catchpoints for the possible parameters of the catch-command. Effectively, please insert a @table @code on line 4844: dynamic printfs immediately. (If you need individual control over the 4842 print commands, simply define normal breakpoints with 4843 explicitly-supplied command lists.) 4844 @table @code <<<< INSERT THIS, and an empty line afterwards 4845 @item gdb 4846 @kindex dprintf-style gdb 4847 Handle the output using the @value{GDBN} @code{printf} command. and @end table on line 4859: 4856 Have the remote debugging agent (such as @code{gdbserver}) handle 4857 the output itself. This style is only available for agents that 4858 support running commands on the target. 4859 @end table <<< INSERT THIS, and an empty line afterwards 4860 @item set dprintf-function @var{function} 4861 Set the function to call if the dprintf style is @code{call}. By 4862 default its value is @code{printf}. You may set it to any expression. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-08-16 21:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-16 21:46 dilyan.palauzov at aegee dot org [this message] 2022-12-23 20:42 ` [Bug gdb/17281] " tromey at sourceware dot org
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-17281-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: linkBe 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).