From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@redhat.com>
Subject: [PATCH 1/3] fix dwarf_decode_line_header
Date: Tue, 18 Jun 2013 19:44:00 -0000 [thread overview]
Message-ID: <1371584669-1687-2-git-send-email-tromey@redhat.com> (raw)
In-Reply-To: <1371584669-1687-1-git-send-email-tromey@redhat.com>
dwarf_decode_line_header has one return that is missing a call to
do_cleanups. This patch adds it.
This was found using the cleanup checker.
* dwarf2read.c (dwarf_decode_line_header): Call do_cleanups
on all return paths.
---
gdb/dwarf2read.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/gdb/dwarf2read.c b/gdb/dwarf2read.c
index 4cd0c0e..bbb8584 100644
--- a/gdb/dwarf2read.c
+++ b/gdb/dwarf2read.c
@@ -15655,6 +15655,7 @@ dwarf_decode_line_header (unsigned int offset, struct dwarf2_cu *cu)
if (line_ptr + lh->total_length > (section->buffer + section->size))
{
dwarf2_statement_list_fits_in_line_number_section_complaint ();
+ do_cleanups (back_to);
return 0;
}
lh->statement_program_end = line_ptr + lh->total_length;
--
1.8.1.4
next prev parent reply other threads:[~2013-06-18 19:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 19:44 [PATCH 0/3] a few more fixes from the cleanup checker Tom Tromey
2013-06-18 19:44 ` [PATCH 3/3] fix solib-som.c Tom Tromey
2013-06-18 19:44 ` Tom Tromey [this message]
2013-06-18 19:51 ` [PATCH 2/3] fix init_cutu_and_read_dies Tom Tromey
2013-07-22 20:25 ` Regression for fission-reread.exp and pr13961.exp [Re: [PATCH 2/3] fix init_cutu_and_read_dies] Jan Kratochvil
2013-07-22 20:49 ` Tom Tromey
2013-07-23 6:50 ` Tom Tromey
2013-07-24 8:02 ` Jan Kratochvil
2013-07-22 17:50 ` [PATCH 0/3] a few more fixes from the cleanup checker Tom Tromey
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=1371584669-1687-2-git-send-email-tromey@redhat.com \
--to=tromey@redhat.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