From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>
Subject: Re: [patch] 2/3: Fix crash on self-looping DW_OP_fbreg
Date: Sun, 04 May 2008 14:14:00 -0000 [thread overview]
Message-ID: <20080504131403.GA26995@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20080501202903.GR22218@caradoc.them.org>
[-- Attachment #1: Type: text/plain, Size: 590 bytes --]
On Thu, 01 May 2008 22:29:04 +0200, Daniel Jacobowitz wrote:
...
> OK. Do we need a cleanup for this though? If we error out, we won't
> get back until we create a new context, so missing the decrement
> is not a problem.
I find it too fragile relying only on the current callers of DWARF_EXPR_EVAL.
There may be a hard to catch bug after someone wraps some part of the code by
CATCH_EXCEPTIONS and expects DWARF_EXPR_CONTEXT passed into the
CATCH_EXCEPTIONS block will stay uncorrupted afterwards.
Attached a discouraged simplified patch not using the exception system.
Regards,
Jan
[-- Attachment #2: gdb-fbreg-loop-nonex.patch --]
[-- Type: text/plain, Size: 2604 bytes --]
2008-05-04 Jan Kratochvil <jan.kratochvil@redhat.com>
* Makefile.in: Update dependencies.
* dwarf2expr.c: New include "gdb_assert.h".
(new_dwarf_expr_context): Initialize MAX_RECURSION_DEPTH.
(dwarf_expr_eval): Sanity check the RECURSION_DEPTH count.
(execute_stack_op): Error out on too large RECURSION_DEPTH.
Increase/decrease RECURSION_DEPTH around the function.
--- ./gdb/Makefile.in 24 Apr 2008 10:21:44 -0000 1.1004
+++ ./gdb/Makefile.in 28 Apr 2008 00:26:38 -0000
@@ -2077,7 +2077,7 @@ dummy-frame.o: dummy-frame.c $(defs_h) $
dfp.o: dfp.c $(defs_h) $(expression_h) $(gdbtypes_h) $(value_h) $(dfp_h) \
$(decimal128_h) $(decimal64_h) $(decimal32_h)
dwarf2expr.o: dwarf2expr.c $(defs_h) $(symtab_h) $(gdbtypes_h) $(value_h) \
- $(gdbcore_h) $(elf_dwarf2_h) $(dwarf2expr_h)
+ $(gdbcore_h) $(elf_dwarf2_h) $(dwarf2expr_h) $(gdb_assert_h)
dwarf2-frame.o: dwarf2-frame.c $(defs_h) $(dwarf2expr_h) $(elf_dwarf2_h) \
$(frame_h) $(frame_base_h) $(frame_unwind_h) $(gdbcore_h) \
$(gdbtypes_h) $(symtab_h) $(objfiles_h) $(regcache_h) \
--- ./gdb/dwarf2expr.c 18 Mar 2008 19:40:47 -0000 1.25
+++ ./gdb/dwarf2expr.c 4 May 2008 13:05:56 -0000
@@ -27,6 +27,7 @@
#include "gdbcore.h"
#include "elf/dwarf2.h"
#include "dwarf2expr.h"
+#include "gdb_assert.h"
/* Local prototypes. */
@@ -46,6 +46,7 @@ new_dwarf_expr_context (void)
retval->stack = xmalloc (retval->stack_allocated * sizeof (CORE_ADDR));
retval->num_pieces = 0;
retval->pieces = 0;
+ retval->max_recursion_depth = 0x100;
return retval;
}
@@ -134,7 +135,13 @@ add_piece (struct dwarf_expr_context *ct
void
dwarf_expr_eval (struct dwarf_expr_context *ctx, gdb_byte *addr, size_t len)
{
+ int old_recursion_depth = ctx->recursion_depth;
+
execute_stack_op (ctx, addr, addr + len);
+
+ /* CTX RECURSION_DEPTH becomes invalid if an exception was thrown here. */
+
+ gdb_assert (ctx->recursion_depth == old_recursion_depth);
}
/* Decode the unsigned LEB128 constant at BUF into the variable pointed to
@@ -281,6 +286,11 @@ execute_stack_op (struct dwarf_expr_cont
ctx->in_reg = 0;
ctx->initialized = 1; /* Default is initialized. */
+ if (ctx->recursion_depth > ctx->max_recursion_depth)
+ error (_("DWARF-2 expression error: Loop detected (%d)."),
+ ctx->recursion_depth);
+ ctx->recursion_depth++;
+
while (op_ptr < op_end)
{
enum dwarf_location_atom op = *op_ptr++;
@@ -739,4 +749,7 @@ execute_stack_op (struct dwarf_expr_cont
dwarf_expr_push (ctx, result);
no_push:;
}
+
+ ctx->recursion_depth--;
+ gdb_assert (ctx->recursion_depth >= 0);
}
next prev parent reply other threads:[~2008-05-04 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 14:44 Jan Kratochvil
2008-05-01 20:29 ` Daniel Jacobowitz
2008-05-04 14:14 ` Jan Kratochvil [this message]
2008-06-05 16:30 ` Daniel Jacobowitz
2008-06-05 18:42 ` Jan Kratochvil
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=20080504131403.GA26995@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=drow@false.org \
--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