From: Jeff Johnston <jjohnstn@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA]: Fix for do_mixed_source_and_assembly in disasm.c
Date: Wed, 17 Dec 2003 21:15:00 -0000 [thread overview]
Message-ID: <3FE0C778.8010606@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
There are a few bugs in do_mixed_source_and_assembly() when dealing with
the ia64. One problem is that cleanups for tuples and lists can
possibly be deferred to a future iteration of a loop, however, the
values are reinitialized to NULL each time at the start of the loop.
Another problem is that the code to figure out if the list/tuple should
be closed off is inside a block of code that is not always reached in
every iteration. These two problems combined to cause a SIGSEGV in gdb
because a NULL pointer gets passed into do_cleanups() which causes all
cleanups to be performed up the chain. I have submitted a separate
patch to prevent running the entire chain when NULL input is passed.
Ok to commit?
-- Jeff J.
2003-12-17 Jeff Johnston <jjohnstn@redhat.com>
* disasm.c (do_mixed_source_and_assembly): For uiout asm list
and tuple cleanups, don't reset to NULL until we close off the
tuple/list. Also move check for whether to close off the
asm tuple/list to where it will be run on each iteration of the
loop.
[-- Attachment #2: disasm.patch --]
[-- Type: text/plain, Size: 1760 bytes --]
Index: disasm.c
===================================================================
RCS file: /cvs/src/src/gdb/disasm.c,v
retrieving revision 1.17
diff -u -p -r1.17 disasm.c
--- disasm.c 24 Oct 2003 17:37:03 -0000 1.17
+++ disasm.c 17 Dec 2003 20:37:25 -0000
@@ -164,6 +164,8 @@ do_mixed_source_and_assembly (struct ui_
CORE_ADDR pc;
int num_displayed = 0;
struct cleanup *ui_out_chain;
+ struct cleanup *ui_out_tuple_chain = NULL;
+ struct cleanup *ui_out_list_chain = NULL;
mle = (struct dis_line_entry *) alloca (nlines
* sizeof (struct dis_line_entry));
@@ -221,8 +223,6 @@ do_mixed_source_and_assembly (struct ui_
for (i = 0; i < newlines; i++)
{
- struct cleanup *ui_out_tuple_chain = NULL;
- struct cleanup *ui_out_list_chain = NULL;
int close_list = 1;
/* Print out everything from next_line to the current line. */
@@ -275,19 +275,21 @@ do_mixed_source_and_assembly (struct ui_
next_line = mle[i].line + 1;
ui_out_list_chain
= make_cleanup_ui_out_list_begin_end (uiout, "line_asm_insn");
- /* Don't close the list if the lines are not in order. */
- if (i < (newlines - 1) && mle[i + 1].line <= mle[i].line)
- close_list = 0;
}
+ /* Don't close the list if the lines are not in order. */
+ if (i < (newlines - 1) && mle[i + 1].line <= mle[i].line)
+ close_list = 0;
+
num_displayed += dump_insns (uiout, di, mle[i].start_pc, mle[i].end_pc,
how_many, stb);
if (close_list)
{
do_cleanups (ui_out_list_chain);
do_cleanups (ui_out_tuple_chain);
+ ui_out_tuple_chain = NULL;
+ ui_out_list_chain = NULL;
ui_out_text (uiout, "\n");
- close_list = 0;
}
if (how_many >= 0)
if (num_displayed >= how_many)
next reply other threads:[~2003-12-17 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-17 21:15 Jeff Johnston [this message]
2003-12-18 22:12 ` Jason Molenda
2003-12-18 23:07 ` J. Johnston
2004-01-02 16:13 ` Andrew Cagney
2004-01-06 19:11 ` J. Johnston
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=3FE0C778.8010606@redhat.com \
--to=jjohnstn@redhat.com \
--cc=gdb-patches@sources.redhat.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