From: Eli Zaretskii <eliz@gnu.org>
To: Caroline Tice <ctice@apple.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH]: Tracking and reporting uninitialized variables
Date: Wed, 02 May 2007 03:10:00 -0000 [thread overview]
Message-ID: <uwszrvs2x.fsf@gnu.org> (raw)
In-Reply-To: <80EE31A6-4DF2-4D1F-B23D-8B814C1E6928@apple.com> (message from Caroline Tice on Tue, 1 May 2007 17:14:39 -0700)
> From: Caroline Tice <ctice@apple.com>
> Date: Tue, 1 May 2007 17:14:39 -0700
> Cc: Caroline Tice <ctice@apple.com>
>
> 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.
Thanks.
What would be really nice is if you'd add a feature whereby I could
catch references to uninitialized variables, something like
(gdb) rwatch foo if uninitialized
That would cause GDB to stop the program whenever it tries to use the
value of a variable that wasn't initialized.
next prev parent reply other threads:[~2007-05-02 3:10 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 [this message]
[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
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=uwszrvs2x.fsf@gnu.org \
--to=eliz@gnu.org \
--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