Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Pedro Alves <pedro@codesourcery.com>,
	sergiodj@linux.vnet.ibm.com,         gdb-patches@sourceware.org
Subject: Re: [RFA] Fix "show convenience" test
Date: Thu, 17 Sep 2009 16:37:00 -0000	[thread overview]
Message-ID: <8ac60eac0909170937t14e62114o9a74d1ef110643b1@mail.gmail.com> (raw)
In-Reply-To: <83ab0uyfzk.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 3127 bytes --]

On Wed, Sep 16, 2009 at 10:08 AM, Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Pedro Alves <pedro@codesourcery.com>
>> Date: Wed, 16 Sep 2009 14:16:22 +0100
>> Cc: gdb-patches@sourceware.org
>>
>> Hmm, I had already approved Paul's similar follow up patch at
>> <http://sourceware.org/ml/gdb-patches/2009-04/msg00105.html>.

I now see that you did. I lost that fact in the ensuing discussion of
testsuite failures :-(

>> I looks like it was waiting for a docs review.
>
> Ouch! sorry about that (binary attachments tend to have this effect on
> me ;-).

The attachment was actually text, just base64-encoded:
Content-Type: text/plain; charset=US-ASCII; name="gdb-convenience.20090406.txt"

Unfortunately, my attempts to convince gmail not to do that have failed :-(

>>  The variable @code{$_siginfo} is bound to extra signal information
>> -inspection (@pxref{extra signal information}).
>> +inspection (@pxref{extra signal information}). Note that @code{$_siginfo}
>> +could be empty. For example, it will be empty before you execute the
>> +@code{run} command.
>>  @end table
>
> A couple of comments:
>
>  . "the variable ... is bound to extra signal information inspection"
>    is awkward wording.  "How about "contains extra signal
>    information"?

Fixed.

>  . I don't understand the note about it being ``empty''?  What does
>    that mean, exactly, and why the example is talking about before
>    `run'?  I could understand that it's empty if no signals were
>    delivered yet, but what does `run' has to do with this?

Before the first 'run' is one rare case where the application has not yet
received any signals. I think this example could be simply removed
without much loss. Let me know if you'd like me to do that.

>
>  . Please leave two spaces between sentences, not one.

Sorry about that.  Fixed.


How does the attached patch look?

Here's the doc part, so you don't have to deal with base64:

Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.624
diff -u -p -u -r1.624 gdb.texinfo
--- doc/gdb.texinfo	15 Sep 2009 18:51:25 -0000	1.624
+++ doc/gdb.texinfo	17 Sep 2009 16:33:19 -0000
@@ -7819,8 +7819,10 @@ the program being debugged terminates.

 @item $_siginfo
 @vindex $_siginfo@r{, convenience variable}
-The variable @code{$_siginfo} is bound to extra signal information
-inspection (@pxref{extra signal information}).
+The variable @code{$_siginfo} contains extra signal information
+(@pxref{extra signal information}).  Note that @code{$_siginfo}
+could be empty, if the application has not yet received any signals.
+For example, it will be empty before you execute the @code{run} command.
 @end table

 On HP-UX systems, if you refer to a function or variable name that


Thanks,
-- 
Paul Pluzhnikov


testsuite/ChangeLog
2009-09-17  Paul Pluzhnikov  <ppluzhnikov@google.com>

	    * gdb.base/default.exp: Fix "show convenience".

doc/ChangeLog
2009-09-17  Paul Pluzhnikov  <ppluzhnikov@google.com>

	    * gdb.texinfo (convenince variables): Mention
	    $_siginfo could be empty.

[-- Attachment #2: gdb-convenience.20090917.txt --]
[-- Type: text/plain, Size: 1911 bytes --]

Index: testsuite/gdb.base/default.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/default.exp,v
retrieving revision 1.31
diff -u -p -u -r1.31 default.exp
--- testsuite/gdb.base/default.exp	13 Aug 2009 14:58:27 -0000	1.31
+++ testsuite/gdb.base/default.exp	17 Sep 2009 16:33:19 -0000
@@ -598,7 +598,7 @@ gdb_test "show complaints" "Max number o
 #test show confirm
 gdb_test "show confirm" "Whether to confirm potentially dangerous operations is o\[a-z\]*." "show confirm"
 #test show convenience
-gdb_test "show convenience" "No debugger convenience variables now defined.(\[^\r\n\]*\[\r\n\])+Convenience variables have names starting with \".\";(\[^\r\n\]*\[\r\n\])+use \"set\" as in \"set .foo = 5\" to define them." "show convenience"
+gdb_test "show convenience" "\\\$_siginfo = void" "show convenience"
 #test show directories
 gdb_test "show directories" "Source directories searched: .cdir\[:;\].cwd" "show directories"
 #test show editing
Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.624
diff -u -p -u -r1.624 gdb.texinfo
--- doc/gdb.texinfo	15 Sep 2009 18:51:25 -0000	1.624
+++ doc/gdb.texinfo	17 Sep 2009 16:33:19 -0000
@@ -7819,8 +7819,10 @@ the program being debugged terminates.
 
 @item $_siginfo
 @vindex $_siginfo@r{, convenience variable}
-The variable @code{$_siginfo} is bound to extra signal information
-inspection (@pxref{extra signal information}).
+The variable @code{$_siginfo} contains extra signal information
+(@pxref{extra signal information}).  Note that @code{$_siginfo}
+could be empty, if the application has not yet received any signals.
+For example, it will be empty before you execute the @code{run} command.
 @end table
 
 On HP-UX systems, if you refer to a function or variable name that

  reply	other threads:[~2009-09-17 16:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16  0:32 Sérgio Durigan Júnior
2009-09-16 13:16 ` Pedro Alves
2009-09-16 17:08   ` Eli Zaretskii
2009-09-17 16:37     ` Paul Pluzhnikov [this message]
2009-09-17 17:26       ` Eli Zaretskii
2009-09-17 17:57         ` Paul Pluzhnikov
2009-09-17 18:16           ` Pedro Alves
2009-09-17 18:29             ` Paul Pluzhnikov
2009-09-17 19:25             ` Joseph S. Myers
2009-09-17 19:52               ` Pedro Alves
2009-09-17 18:26           ` 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=8ac60eac0909170937t14e62114o9a74d1ef110643b1@mail.gmail.com \
    --to=ppluzhnikov@google.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=sergiodj@linux.vnet.ibm.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