From: Doug Evans <dje@google.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [MI] core awareness
Date: Tue, 12 Jan 2010 23:08:00 -0000 [thread overview]
Message-ID: <e394668d1001121508l265cefi6b1b8b8ab5a3ed74@mail.gmail.com> (raw)
In-Reply-To: <e394668d1001121456m2b9d206dpa1ffdccddfcd369d@mail.gmail.com>
On Tue, Jan 12, 2010 at 2:56 PM, Doug Evans <dje@google.com> wrote:
> On Tue, Jan 12, 2010 at 1:43 PM, Vladimir Prus
> <vladimir@codesourcery.com> wrote:
>> Thanks. Here's the version I've just checked in. Differs from above in:
>>
>> - mi-support.exp fix to make it not crash on the 'core' field
>> - demand_private_info now initialized 'extra' to 0, and does not rely
>> on luck.
>
> Hi.
>
> Nit: features/threads.dtd didn't get checked in.
>
Sorry, one more nit.
I'm getting a build failure:
cc1: warnings being treated as errors
../../../src/gdb/mi/mi-main.c: In function 'mi_cmd_list_thread_groups':
../../../src/gdb/mi/mi-main.c:518: warning: 'tree' may be used
uninitialized in this function
../../../src/gdb/mi/mi-main.c:518: note: 'tree' was declared here
make: *** [mi-main.o] Error 1
Checked in as obvious.
2010-01-12 Doug Evans <dje@google.com>
* mi/mi-main.c (list_available_thread_groups): Avoid "may be used
uninitialized" warning from gcc on local `tree'.
Index: mi/mi-main.c
===================================================================
RCS file: /cvs/src/src/gdb/mi/mi-main.c,v
retrieving revision 1.162
diff -u -p -r1.162 mi-main.c
--- mi/mi-main.c 12 Jan 2010 21:40:24 -0000 1.162
+++ mi/mi-main.c 12 Jan 2010 23:00:51 -0000
@@ -513,9 +513,10 @@ list_available_thread_groups (VEC (int)
struct osdata_item *item;
int ix_items;
/* This keeps a map from integer (pid) to VEC (struct osdata_item *)*
- The vector contains information about all threads for the given
- pid. */
- splay_tree tree;
+ The vector contains information about all threads for the given pid.
+ This is assigned an initial value to avoid "may be used uninitialized"
+ warning from gcc. */
+ splay_tree tree = NULL;
/* get_osdata will throw if it cannot return data. */
data = get_osdata ("processes");
next prev parent reply other threads:[~2010-01-12 23:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 15:33 Pedro Alves
2009-12-21 14:48 ` Vladimir Prus
2009-12-31 11:51 ` Pedro Alves
2010-01-04 15:11 ` Vladimir Prus
2010-01-08 20:30 ` Pedro Alves
2010-01-09 12:41 ` Vladimir Prus
2010-01-09 13:48 ` Eli Zaretskii
2010-01-11 14:17 ` Pedro Alves
2010-01-11 21:01 ` Vladimir Prus
2010-01-11 21:22 ` Pedro Alves
2010-01-12 21:44 ` Vladimir Prus
2010-01-12 22:56 ` Doug Evans
2010-01-12 23:08 ` Doug Evans [this message]
2010-01-13 5:21 ` Vladimir Prus
-- strict thread matches above, loose matches on Subject: below --
2009-12-16 20:53 Vladimir Prus
2009-12-17 15:31 ` Pedro Alves
2009-12-18 11:41 ` 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=e394668d1001121508l265cefi6b1b8b8ab5a3ed74@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=vladimir@codesourcery.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