Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Caroline Tice <ctice@apple.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Ping!  [PATCH]: Tracking and reporting uninitialized variables
Date: Wed, 09 May 2007 00:33:00 -0000	[thread overview]
Message-ID: <m3odkuhm31.fsf@codesourcery.com> (raw)
In-Reply-To: <717BDA2E-D6FF-4AA5-B857-68BA5B140F5F@apple.com> (Caroline Tice's message of "Tue, 8 May 2007 09:26:35 -0700")


Caroline Tice <ctice@apple.com> writes:
>> As part of some work I have been doing on improving debugging of
>> optimized code, I
>> have created a GCC patch that tags variables it believes are
>> uninitialized with a new
>> Dwarf op (an extension), DW_OP_GNU_uninit.   I have submitted that
>> patch to the
>> GCC patches list and am waiting for approval to commit it.   I have
>> also created the
>> following gdb patch to recognize the new op and inform the user when
>> a variable
>> the user requests to see is uninitialized.
>>
>> I have tested this patch on some small testcases and I have run the
>> gdb dejagnu
>> testsuite with no regressions.  I am new to submitting things to
>> this list, so if there
>> is anything else I ought to have done, please let me know
>> (kindly!).

Hi, Caroline.  This seems like a nice patch.

In a multi-piece location expression, can each piece be individually
initialized or uninitialized?  If that's so, then there should also be
an 'initialized' member of 'struct dwarf_expr_piece', which gets set
appropriately for each piece in a multi-piece location expression.

Either way, the code for DW_OP_GNU_uninit should check that it's the
last opcode in the piece or in the entire expression, as the
DW_OP_reg* cases do.

I think the 'struct dwarf_expr_context' member should be named
simply 'initialized', instead of 'var_status'.  The 'struct value'
field should be named 'initialized', and the accessor functions should
be named 'value_initialized' and 'set_value_initialized'.  The comment
in value.h actually needs to be filled in; the description should be
thorough enough to allow someone who otherwise knows how GDB works to
use those functions, without reading their definitions.

I couldn't see from your patch why 'signed_address_type',
'unsigned_address_type', and 'add_piece' were made visible outside
dwarf2expr.c; that should be left out of the patch if it's not needed.

Have you filed a copyright assignment with the FSF?


  reply	other threads:[~2007-05-09  0:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02  0:14 Caroline Tice
2007-05-02  3:10 ` Eli Zaretskii
     [not found]   ` <233FDE1A-ABAF-40E9-9799-0B6938D8BE2E@apple.com>
2007-05-03  3:06     ` Eli Zaretskii
2007-05-08 16:26 ` Ping! " Caroline Tice
2007-05-09  0:33   ` Jim Blandy [this message]
2007-05-09  0:38     ` Jim Ingham
2007-05-09  1:09       ` Jim Blandy
2007-05-09 17:36     ` Caroline Tice
2007-05-09 21:04       ` Caroline Tice
2007-05-16 23:35         ` Jim Blandy
2007-05-17 17:18           ` Caroline Tice
2007-05-18  0:00             ` Jim Blandy
2007-05-18 16:38               ` Caroline Tice
2007-05-18 17:05                 ` Jim Blandy
2007-05-18 17:14                   ` Daniel Jacobowitz

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=m3odkuhm31.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=ctice@apple.com \
    --cc=gdb-patches@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