From: Elena Zannoni <ezannoni@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: ac131313@redhat.com, gdb@sources.redhat.com
Subject: Re: gdb crash with -i=mi2
Date: Fri, 08 Aug 2003 18:13:00 -0000 [thread overview]
Message-ID: <16179.59905.880712.656312@localhost.redhat.com> (raw)
In-Reply-To: <200308081712.h78HCqKM015964@duracef.shout.net>
Try this as a workaround, seems to work for me:
Index: mi-interp.c
===================================================================
RCS file: /cvs/uberbaum/gdb/mi/mi-interp.c,v
retrieving revision 1.5
diff -u -p -r1.5 mi-interp.c
--- mi-interp.c 7 Aug 2003 17:47:42 -0000 1.5
+++ mi-interp.c 8 Aug 2003 18:12:49 -0000
@@ -409,7 +409,7 @@ _initialize_mi_interp (void)
/* The various interpreter levels. */
interp_add (interp_new (INTERP_MI1, NULL, mi_out_new (1), &procs));
- interp_add (interp_new (INTERP_MI2, NULL, mi_out_new (2), &procs));
+ /*interp_add (interp_new (INTERP_MI2, NULL, mi_out_new (2), &procs));*/
interp_add (interp_new (INTERP_MI3, NULL, mi_out_new (3), &procs));
/* "mi" selects the most recent released version. "mi2" was
Michael Elizabeth Chastain writes:
> The new mi2 tests are bombing out big time for me!
>
> % gdb -i=mi2
> Segmentation fault (core dumped)
>
> Here is a backtrace.
>
> #0 0x080c6e2a in interp_set (interp=0x0)
> at /berman/fsf/_today_/source/gdb/HEAD/src/gdb/interps.c:160
> #1 0x080c6ee5 in interp_set (interp=0x82a1bc8)
> at /berman/fsf/_today_/source/gdb/HEAD/src/gdb/interps.c:186
> #2 0x08077d69 in captured_main (data=0x0)
> at /berman/fsf/_today_/source/gdb/HEAD/src/gdb/main.c:582
> #3 0x0810cd91 in do_catch_errors (uiout=0x8261fa0, data=0x1)
> at /berman/fsf/_today_/source/gdb/HEAD/src/gdb/top.c:497
> #4 0x0810ccc0 in catcher (func=0x810cd80 <do_catch_errors>,
> func_uiout=0x8261fa0, func_args=0xbffff7d0, func_val=0xbffff7c8,
> func_caught=0xbffff7cc, errstring=0x1 <Address 0x1 out of bounds>, mask=6)
> at /berman/fsf/_today_/source/gdb/HEAD/src/gdb/top.c:429
> #5 0x0810cdea in catch_errors (func=0x1, func_args=0x1,
> errstring=0x1 <Address 0x1 out of bounds>, mask=1)
> at /berman/fsf/_today_/source/gdb/HEAD/src/gdb/top.c:509
> #6 0x08078591 in gdb_main (args=0x829b5c0)
> at /berman/fsf/_today_/source/gdb/HEAD/src/gdb/main.c:820
> #7 0x0807772e in main (argc=1, argv=0x1)
> at /berman/fsf/_today_/source/gdb/HEAD/src/gdb/gdb.c:35
> #8 0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6
>
> This happens with:
>
> gdb HEAD 2003-08-07 20:28:13 UTC
>
> It also happens with:
>
> gdb HEAD 2003-08-07 20:31:55 UTC
>
> native i686-pc-linux-gnu, red hat linux 8.
> gdb built with gcc 3.3, binutils 2.14.
>
> It's happening in this code:
>
> 180 /* Clear out any installed interpreter hooks/event handlers. */
> 181 clear_interpreter_hooks ();
> 182
> 183 if (interp->procs->resume_proc != NULL
> 184 && (!interp->procs->resume_proc (interp->data)))
> 185 {
> 186 if (!interp_set (old_interp))
> 187 internal_error (__FILE__, __LINE__,
> 188 "Failed to initialize new interp \"%s\" %s",
> 189 interp->name, "and could not restore old interp!
> \n");
>
> This is calling interp_set recursively with old_interp=0x0
> (as shown in the stack trace).
>
> Michael C
prev parent reply other threads:[~2003-08-08 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 17:12 Michael Elizabeth Chastain
2003-08-08 18:13 ` Elena Zannoni [this message]
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=16179.59905.880712.656312@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mec@shout.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).