Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Hui Zhu <teawater@gmail.com>,
	gdb-patches ml <gdb-patches@sourceware.org>,
	       Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH] Fix gdb crash with tui
Date: Tue, 12 Mar 2013 16:04:00 -0000	[thread overview]
Message-ID: <513F51D9.9040604@redhat.com> (raw)
In-Reply-To: <20130312123654.GA12204@host2.jankratochvil.net>

On 03/12/2013 12:36 PM, Jan Kratochvil wrote:
> On Tue, 12 Mar 2013 13:21:44 +0100, Hui Zhu wrote:
>> Not sure the prev backtrace for crash is right, so I post new one:
> 
> BTW don't you have a recipe for the reproducibility?  Don't you have some
> unusual terminal size (stty size) for example?  Which distro?
> 
> 
> Jan

I just reproduced it on my Fedora 17 box with current mainline.

$ stty size
45 172

To reproduce, I just did the steps in the OP.

$ ./gdb ./gdb
(gdb) start

"c-x a" to flip to TUI mode.

repeat:
 press arrow up a bit, so the source display scrolls a bit up.
 press arrow down a bit, so the source display scrolls a bit down.
 goto repeat until

 "---Type <return> to continue, or q <return> to quit---"

appears in TUI's console.  Then press return.

(top-gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x000000000072ea9a in rl_callback_read_char () at ../../src/readline/callback.c:220
#2  0x00000000005e1c9d in rl_callback_read_char_wrapper (client_data=0x0) at ../../src/gdb/event-top.c:163
#3  0x00000000005e207e in stdin_event_handler (error=0, client_data=0x0) at ../../src/gdb/event-top.c:371
#4  0x00000000005e0c22 in handle_file_event (data=...) at ../../src/gdb/event-loop.c:768
#5  0x00000000005e00cb in process_event () at ../../src/gdb/event-loop.c:342
#6  0x00000000005e0192 in gdb_do_one_event () at ../../src/gdb/event-loop.c:406
#7  0x00000000005e01e3 in start_event_loop () at ../../src/gdb/event-loop.c:431
#8  0x00000000005e1cc7 in cli_command_loop () at ../../src/gdb/event-top.c:176
#9  0x00000000005d8768 in current_interp_command_loop () at ../../src/gdb/interps.c:331
#10 0x00000000005d91a6 in captured_command_loop (data=0x0) at ../../src/gdb/main.c:256
#11 0x00000000005d7512 in catch_errors (func=0x5d918b <captured_command_loop>, func_args=0x0, errstring=0x88f8d4 "", mask=6) at ../../src/gdb/exceptions.c:546
#12 0x00000000005da5b9 in captured_main (data=0x7fff21b3eea0) at ../../src/gdb/main.c:1033
#13 0x00000000005d7512 in catch_errors (func=0x5d9442 <captured_main>, func_args=0x7fff21b3eea0, errstring=0x88f8d4 "", mask=6) at ../../src/gdb/exceptions.c:546
#14 0x00000000005da5ef in gdb_main (args=0x7fff21b3eea0) at ../../src/gdb/main.c:1042
#15 0x000000000045a00a in main (argc=2, argv=0x7fff21b3efa8) at ../../src/gdb/gdb.c:34
(top-gdb)

-- 
Pedro Alves


  parent reply	other threads:[~2013-03-12 16:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09 14:14 Hui Zhu
2013-03-11 19:25 ` Jan Kratochvil
2013-03-12  3:15   ` Hui Zhu
2013-03-12 12:22     ` Hui Zhu
2013-03-12 12:37       ` Jan Kratochvil
2013-03-12 13:21         ` Hui Zhu
2013-03-12 14:21           ` Hui Zhu
2013-03-12 16:04         ` Pedro Alves [this message]
2013-03-12 16:35           ` Pedro Alves
2013-03-12 18:36 ` Pedro Alves
2013-03-12 18:42   ` Pedro Alves
2013-03-13 18:55   ` [patch+7.6] [TUI] Fix scrolling missing '>' 7.6 regression [Re: [PATCH] Fix gdb crash with tui] Jan Kratochvil
2013-03-14  1:46     ` Hui Zhu
2013-03-14 12:53     ` Pedro Alves
2013-03-14 14:44       ` [commit+7.6] " Jan Kratochvil
2013-03-13 18:55   ` [patch+7.6] [TUI] Fix scrolling crash " Jan Kratochvil
2013-03-14  1:46     ` Hui Zhu
2013-03-14 12:33     ` Pedro Alves
2013-03-14 14:41       ` [commit+7.6] " Jan Kratochvil
2013-03-14 14:57         ` Pedro Alves

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=513F51D9.9040604@redhat.com \
    --to=palves@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=teawater@gmail.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