Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org,  brobecker@adacore.com,
	 qiyaoltc@gmail.com,  palves@redhat.com
Subject: Re: [PATCH v2] Add support for the --readnever command-line option
Date: Sat, 25 Nov 2017 16:41:00 -0000	[thread overview]
Message-ID: <87indytiov.fsf@redhat.com> (raw)
In-Reply-To: <83k1ye95ju.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 25 Nov	2017 09:32:53 +0200")

Thanks for the review, Eli.

On Saturday, November 25 2017, Eli Zaretskii wrote:

>> From: Sergio Durigan Junior <sergiodj@redhat.com>
>> Cc: Joel Brobecker <brobecker@adacore.com>,
>> 	Yao Qi <qiyaoltc@gmail.com>,
>> 	Pedro Alves <palves@redhat.com>,
>> 	Eli Zaretskii <eliz@gnu.org>,
>> 	Sergio Durigan Junior <sergiodj@redhat.com>
>> Date: Fri, 24 Nov 2017 18:01:22 -0500
>> 
>> diff --git a/gdb/NEWS b/gdb/NEWS
>> index 754ce103bd..32229d3cea 100644
>> --- a/gdb/NEWS
>> +++ b/gdb/NEWS
>> @@ -3,6 +3,10 @@
>>  
>>  *** Changes since GDB 8.0
>>  
>> +* New "--readnever" command line option instructs GDB to not read each
>> +  symbol file's symbolic debug information.  This makes startup faster
>> +  but at the expense of not being able to perform symbolic debugging.
>> +
>
> This part is okay, but I would add here as well a hint about the use
> cases this supports.  Like this, for example:
>
>   This option is intended for use cases where symbolic debugging will
>   not be used, e.g., when you only need to dump the debuggee's core.

Good point.  I added the text.

>> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
>> index 00451d243d..f3eef8dfeb 100644
>> --- a/gdb/doc/gdb.texinfo
>> +++ b/gdb/doc/gdb.texinfo
>> @@ -1037,6 +1037,15 @@ Read each symbol file's entire symbol table immediately, rather than
>>  the default, which is to read it incrementally as it is needed.
>>  This makes startup slower, but makes future operations faster.
>>  
>> +@item --readnever
>> +@cindex @code{--readnever}
>> +Do not read each symbol file's symbolic debug information.  This makes
>> +startup faster but at the expense of not being able to perform
>> +symbolic debugging.  DWARF unwind information is also not read,
>> +meaning backtraces may become incomplete or inaccurate.  One use of
>> +this is when a user simply wants to do the following sequence: attach,
>> +dump core, detach.  Loading the debugging information in this case is
>> +an unnecessary cause of delay.
>>  @end table
>>  
>>  @node Mode Options
>> @@ -18486,6 +18495,14 @@ tables by using the @samp{-readnow} option with any of the commands that
>>  load symbol table information, if you want to be sure @value{GDBN} has the
>>  entire symbol table available.
>>  
>> +@kindex readnever
>> +@cindex never read symbols
>> +@cindex symbols, never read
>> +@item symbol-file @r{[} -readnever @r{]} @var{filename}
>> +@itemx file @r{[} -readnever @r{]} @var{filename}
>> +You can instruct @value{GDBN} to never read the symbolic information
>> +contained in @var{filename} by using the @samp{-readnever} option.
>> +
>
> This will cause index entries about "readnever" point to 2 different
> places, with no way for the reader to tell up front which place is
> about where they want to go.  So I suggest to change the index entries
> as follows:
>
>   @cindex @code{--readnever}, command-line option
>   ...
>   @cindex @code{-readnever}, option for symbol-file command
>
> (Note that I switched from @kindex to @cindex, since @kindex is used
> for command names, and -readnever isn't.)

Hm, I see.  To be clear, I copied the entry above, which uses @kindex
for the "readnow" symbol-file command.  Maybe that should be fixed (in
another patch), too?

> Otherwise, the patch for the manual is OK.
>
>> @@ -1183,6 +1213,9 @@ Selection of debuggee and its files:\n\n\
>>    --se=FILE          Use FILE as symbol file and executable file.\n\
>>    --symbols=SYMFILE  Read symbols from SYMFILE.\n\
>>    --readnow          Fully read symbol files on first access.\n\
>> +  --readnever        Do not read symbol files.\n\
>> +                     There is currently a known limitation that this only\n\
>> +                     has an effect on symbol files provided in DWARF format.\n\
>
> The part about its being limited to DWARF should now go away, right?

Right, I forgot to remove this line.  Did it now.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  reply	other threads:[~2017-11-25 16:41 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06 20:54 [RFC/RFA] Add support for the --readnever command-line option (DWARF only) Joel Brobecker
2016-07-12 14:27 ` Yao Qi
2016-10-04 18:07   ` Pedro Alves
2017-11-23  0:54     ` [PATCH v2] " Sergio Durigan Junior
2017-11-23 12:09       ` Pedro Alves
2017-11-23 17:21         ` Sergio Durigan Junior
2017-11-23 17:29           ` Pedro Alves
2017-11-24  4:54             ` Sergio Durigan Junior
2017-11-24 13:18               ` Pedro Alves
2017-11-24 20:27                 ` Sergio Durigan Junior
2017-11-27 19:13                   ` Pedro Alves
2017-11-29  0:59                     ` Sergio Durigan Junior
2017-11-29 12:23                       ` Pedro Alves
2017-11-23 15:59       ` Eli Zaretskii
2017-11-23 19:36         ` Sergio Durigan Junior
2016-10-04 18:06 ` [RFC/RFA] " Pedro Alves
2017-11-24 23:01 ` [PATCH v2] Add support for the --readnever command-line option Sergio Durigan Junior
2017-11-25  7:33   ` Eli Zaretskii
2017-11-25 16:41     ` Sergio Durigan Junior [this message]
2017-11-25 17:16       ` Eli Zaretskii
2017-11-29  1:21 ` [PATCH v3] Add support for the readnever concept Sergio Durigan Junior
2017-11-29  3:39   ` Eli Zaretskii
2017-11-29 12:25   ` Pedro Alves
2017-11-29 18:43     ` Sergio Durigan Junior
2017-11-29 21:45     ` [PATCH] Make 'symbol-file' not care about the position of command line arguments Sergio Durigan Junior
2017-11-29 22:26       ` Pedro Alves
2017-11-29 22:42         ` Sergio Durigan Junior
2017-11-29 23:15           ` Pedro Alves
2017-11-30  0:08             ` Sergio Durigan Junior
2017-11-30  0:34               ` Pedro Alves
2017-11-30  4:07                 ` Sergio Durigan Junior
2017-11-30  4:25       ` [PATCH v2] Make '{add-,}symbol-file' " Sergio Durigan Junior
2017-11-30 10:57         ` Pedro Alves
2017-11-30 12:38           ` Sergio Durigan Junior
2017-11-30 12:49             ` Pedro Alves
2017-11-30 13:06               ` Sergio Durigan Junior
2017-11-30 13:33       ` [PATCH v3] " Sergio Durigan Junior
2017-11-30 15:01         ` Pedro Alves
2017-11-30 17:26           ` Sergio Durigan Junior
2017-11-30 17:37             ` Pedro Alves
2017-11-30 17:43               ` Sergio Durigan Junior
2017-11-30 17:50                 ` Pedro Alves
2017-11-30 20:00       ` [PATCH v4] " Sergio Durigan Junior
2017-12-01 12:11         ` Pedro Alves
2017-12-01 17:41           ` Sergio Durigan Junior
2017-12-01 21:45             ` Pedro Alves
2017-12-01 22:02               ` Sergio Durigan Junior
2017-11-30  0:25 ` [PATCH v4] Add support for the readnever concept Sergio Durigan Junior
2017-11-30 11:53   ` Pedro Alves
2017-12-01  4:35     ` Sergio Durigan Junior
2017-12-01 12:43       ` Pedro Alves
2017-12-01 17:19         ` Tom Tromey
2017-12-01 17:21           ` Sergio Durigan Junior
2017-12-01 20:00             ` Pedro Alves
2017-12-01 22:16 ` [PATCH v5] " Sergio Durigan Junior
2017-12-01 23:19   ` Pedro Alves
2017-12-02  2:31     ` Sergio Durigan Junior
2017-12-02  8:21   ` Eli Zaretskii

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=87indytiov.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=qiyaoltc@gmail.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