From: Vladimir Prus <vladimir@codesourcery.com>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [MI non-stop 04/11] Implement --thread and --frame.
Date: Sun, 13 Jul 2008 03:54:00 -0000 [thread overview]
Message-ID: <200807130754.14849.vladimir@codesourcery.com> (raw)
In-Reply-To: <200807122014.m6CKEgkP016422@d12av02.megacenter.de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 592 bytes --]
On Sunday 13 July 2008 00:14:42 Ulrich Weigand wrote:
> Vladimir Prus wrote:
>
> > mi_cmd_execute (struct mi_parse *parse)
> > {
> > struct cleanup *cleanup = make_cleanup (null_cleanup, NULL);
> > + char *thread_str;
> > + char *frame_str;
> > + int thread;
> > + int i;
>
> [snip]
>
> > + error (_("Invalid frame id: %s"), frame_str);
>
> This variable is used uninitialized, which breaks the -Werror
> build for me.
>
> (Also, it seems the other local variables introduced by this
> patch are never used ...)
Apologies. I've checked in the attached to fix this.
- Volodya
[-- Attachment #2: commit.diff --]
[-- Type: text/x-diff, Size: 1340 bytes --]
Index: gdb/ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/ChangeLog,v
retrieving revision 1.9550
diff -u -p -r1.9550 ChangeLog
--- gdb/ChangeLog 12 Jul 2008 17:10:59 -0000 1.9550
+++ gdb/ChangeLog 13 Jul 2008 03:51:22 -0000
@@ -1,3 +1,8 @@
+2008-07-13 Vladimir Prus <vladimir@codesourcery.com>
+
+ * mi/mi-main.c (mi_cmd_execute): Remove unused variable.
+ Fix printing of frame, when frame is wrong.
+
2008-07-12 Vladimir Prus <vladimir@codesourcery.com>
Implement -exec-continue/-exec-interrupt --all.
Index: gdb/mi/mi-main.c
===================================================================
RCS file: /cvs/src/src/gdb/mi/mi-main.c,v
retrieving revision 1.126
diff -u -p -r1.126 mi-main.c
--- gdb/mi/mi-main.c 12 Jul 2008 17:10:59 -0000 1.126
+++ gdb/mi/mi-main.c 13 Jul 2008 03:51:22 -0000
@@ -1068,9 +1068,6 @@ static void
mi_cmd_execute (struct mi_parse *parse)
{
struct cleanup *cleanup;
- char *thread_str;
- char *frame_str;
- int thread;
int i;
free_all_values ();
@@ -1101,7 +1098,7 @@ mi_cmd_execute (struct mi_parse *parse)
/* find_relative_frame was successful */
select_frame (fid);
else
- error (_("Invalid frame id: %s"), frame_str);
+ error (_("Invalid frame id: %d"), frame);
}
if (parse->cmd->argv_func != NULL)
next prev parent reply other threads:[~2008-07-13 3:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 16:54 Vladimir Prus
2008-06-28 17:30 ` Eli Zaretskii
2008-06-28 18:00 ` Vladimir Prus
2008-06-28 18:23 ` Eli Zaretskii
2008-06-28 18:26 ` Marc Khouzam
2008-06-29 6:10 ` Vladimir Prus
2008-06-29 20:15 ` Eli Zaretskii
2008-07-01 3:53 ` Vladimir Prus
2008-06-30 18:35 ` Michael Snyder
2008-06-30 18:42 ` Daniel Jacobowitz
2008-06-28 18:13 ` Marc Khouzam
2008-06-28 18:26 ` Eli Zaretskii
2008-06-28 18:27 ` Marc Khouzam
2008-06-29 6:08 ` Vladimir Prus
2008-06-29 19:42 ` Eli Zaretskii
2008-06-30 0:09 ` Tom Tromey
2008-06-30 8:39 ` Eli Zaretskii
2008-06-30 18:35 ` Michael Snyder
2008-06-30 19:19 ` Tom Tromey
2008-06-30 20:47 ` Daniel Jacobowitz
2008-07-11 12:50 ` Daniel Jacobowitz
2008-07-12 20:15 ` Ulrich Weigand
2008-07-13 3:54 ` Vladimir Prus [this message]
2008-07-15 18:42 ` Ulrich Weigand
2008-07-13 5:45 ` Vladimir Prus
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=200807130754.14849.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
--cc=uweigand@de.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