Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: [HEADS-UP] gdb segfault
Date: Sat, 08 May 2004 03:18:00 -0000	[thread overview]
Message-ID: <409C5170.8040702@redhat.com> (raw)

Hey yo --

gdb is seg-faulting immediately whenever its run with --noasync.
I have an old build from the beginning of March that doesn't
do it (nor do even older ones), so it's probably a change
from between then and now.

It crashes in display_gdb_prompt, as called from
tui_command_loop.  Here's a backtrace.


#0  0x40106d33 in strlen () from /lib/tls/libc.so.6
#1  0x08114c6a in display_gdb_prompt (new_prompt=0x0)
     at /home/msnyder/src/gdb/event-top.c:280
#2  0x080bf1f5 in tui_command_loop (data=0x0)
     at /home/msnyder/src/gdb/tui/tui-interp.c:140
#3  0x0811168a in current_interp_command_loop ()
     at /home/msnyder/src/gdb/interps.c:277
#4  0x0807aafb in captured_command_loop (data=0x0)
     at /home/msnyder/src/gdb/main.c:97
#5  0x080801d9 in do_catch_errors (uiout=0x830b0c0, data=0xbfffbe18)
     at /home/msnyder/src/gdb/top.c:524
#6  0x0807ffdc in catcher (func=0x80801bd <do_catch_errors>,
     func_uiout=0x830b0c0, func_args=0xbfffbe18, func_val=0xbfffbe24,
     func_caught=0xbfffbe20, errstring=0x822cc48 "", gdberrmsg=0x0, mask=6)
     at /home/msnyder/src/gdb/top.c:431
#7  0x08080214 in catch_errors (func=0x807aaf0 <captured_command_loop>,
     func_args=0x0, errstring=0x822cc48 "", mask=6)
     at /home/msnyder/src/gdb/top.c:536
#8  0x0807b918 in captured_main (data=0xbfffc140)
     at /home/msnyder/src/gdb/main.c:805
#9  0x080801d9 in do_catch_errors (uiout=0x82b8220, data=0xbfffc0f8)
     at /home/msnyder/src/gdb/top.c:524
#10 0x0807ffdc in catcher (func=0x80801bd <do_catch_errors>,
     func_uiout=0x82b8220, func_args=0xbfffc0f8, func_val=0xbfffc104,
     func_caught=0xbfffc100, errstring=0x822cc48 "", gdberrmsg=0x0, mask=6)
     at /home/msnyder/src/gdb/top.c:431
#11 0x08080214 in catch_errors (func=0x807ab2e <captured_main>,
     func_args=0xbfffc140, errstring=0x822cc48 "", mask=6)
     at /home/msnyder/src/gdb/top.c:536
#12 0x0807b942 in gdb_main (args=0xbfffc140)
     at /home/msnyder/src/gdb/main.c:814
#13 0x0807aae9 in main (argc=2, argv=0xbfffc1e4)
     at /home/msnyder/src/gdb/gdb.c:35


             reply	other threads:[~2004-05-08  3:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-08  3:18 Michael Snyder [this message]
     [not found] ` <40A0272D.5080702@gnu.org>
2004-06-01 16:08   ` Elena Zannoni
2004-06-01 17:41     ` Michael Snyder
2004-06-10 16:22       ` Andrew Cagney
2004-06-11 14:42         ` Eli Zaretskii
2004-07-17  3:24         ` Andrew Cagney

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=409C5170.8040702@redhat.com \
    --to=msnyder@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