From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Revert: [obv] Code cleanup: Move print_command_1 expr variable scope
Date: Fri, 27 Mar 2015 19:22:00 -0000 [thread overview]
Message-ID: <20150327192231.GA21247@host1.jankratochvil.net> (raw)
In-Reply-To: <5515AC41.1040907@ericsson.com>
[-- Attachment #1: Type: text/plain, Size: 618 bytes --]
Hi Simon,
On Fri, 27 Mar 2015 20:15:13 +0100, Simon Marchi wrote:
> I think this patch is wrong. Starting with that commit (f30d5c7),
> some tests (e.g. mi-break.exp) started to fail for me, because
> of gdb segfaulting. Backtrace here: http://paste.ubuntu.com/10690836/
>
> The address of expr is passed to the cleanup. When the cleanup is ran,
> expr is no longer in scope, so what is at that address is probably not
> safe to use anymore. That's my guess.
yes, you are sure right, I have reverted it now.
Sorry I made that commit somehow automatically, not expecting it may have any
side effects.
Thanks,
Jan
[-- Attachment #2: Type: message/rfc822, Size: 1990 bytes --]
From: Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: [PATCH] Revert: Code cleanup: Move print_command_1 expr variable scope
Date: Fri, 27 Mar 2015 20:19:37 +0100
Simon Marchi:
I think this patch is wrong. Starting with that commit (f30d5c7),
some tests (e.g. mi-break.exp) started to fail for me, because
of gdb segfaulting.
The address of expr is passed to the cleanup. When the cleanup is ran,
expr is no longer in scope, so what is at that address is probably not
safe to use anymore. That's my guess.
gdb/ChangeLog
2015-03-27 Jan Kratochvil <jan.kratochvil@redhat.com>
Revert:
2015-03-26 Jan Kratochvil <jan.kratochvil@redhat.com>
Code cleanup.
* printcmd.c (print_command_1): Move expr variable scope.
---
gdb/ChangeLog | 7 +++++++
gdb/printcmd.c | 3 +--
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 72940b0..6c6b94e 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,10 @@
+2015-03-27 Jan Kratochvil <jan.kratochvil@redhat.com>
+
+ Revert:
+ 2015-03-26 Jan Kratochvil <jan.kratochvil@redhat.com>
+ Code cleanup.
+ * printcmd.c (print_command_1): Move expr variable scope.
+
2015-03-27 Joel Brobecker <brobecker@adacore.com>
* dtrace-probe.c (dtrace_process_dof_probe): Initialize expr to NULL.
diff --git a/gdb/printcmd.c b/gdb/printcmd.c
index a1451f8..deb501a 100644
--- a/gdb/printcmd.c
+++ b/gdb/printcmd.c
@@ -946,6 +946,7 @@ validate_format (struct format_data fmt, const char *cmdname)
static void
print_command_1 (const char *exp, int voidprint)
{
+ struct expression *expr;
struct cleanup *old_chain = make_cleanup (null_cleanup, NULL);
char format = 0;
struct value *val;
@@ -968,8 +969,6 @@ print_command_1 (const char *exp, int voidprint)
if (exp && *exp)
{
- struct expression *expr;
-
expr = parse_expression (exp);
make_cleanup (free_current_contents, &expr);
val = evaluate_expression (expr);
--
2.1.0
next prev parent reply other threads:[~2015-03-27 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 17:46 Jan Kratochvil
2015-03-27 19:15 ` Simon Marchi
2015-03-27 19:22 ` Jan Kratochvil [this message]
2015-03-27 19:24 ` Revert: " Simon Marchi
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=20150327192231.GA21247@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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