public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tui/14486] New: resize crashes tui Date: Fri, 17 Aug 2012 20:08:00 -0000 [thread overview] Message-ID: <bug-14486-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14486 Bug #: 14486 Summary: resize crashes tui Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: tui AssignedTo: unassigned@sourceware.org ReportedBy: hjl.tools@gmail.com Classification: Unclassified [hjl@gnu-6 gdb]$ gdb gdb GNU gdb (GDB) 7.4.50.20120707-cvs Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /export/build/gnu/gdb/build-x86_64-linux/gdb/gdb...done. Setting up the environment for debugging gdb. Breakpoint 1 at 0x6c430e: file /export/gnu/import/git/gdb/gdb/utils.c, line 897. Breakpoint 2 at 0x4d621c: file /export/gnu/import/git/gdb/gdb/cli/cli-cmds.c, line 223. (top-gdb) b main Breakpoint 3 at 0x456f5b: file /export/gnu/import/git/gdb/gdb/gdb.c, line 29. (top-gdb) r Starting program: /export/build/gnu/gdb/build-x86_64-linux/gdb/gdb [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Breakpoint 3, During symbol reading, incomplete CFI data; unspecified registers (e.g., rax) at 0x456f9b. main (argc=1, argv=0x7fffffffdee8) at /export/gnu/import/git/gdb/gdb/gdb.c:29 29 memset (&args, 0, sizeof args); (top-gdb) layout asm Resize window (top-gdb) si tui crashed: (top-gdb) bt #0 0x00000000004efb22 in tui_source_is_displayed (fname=0x593ce10 "bug4.js") at /export/gnu/import/git/gdb/gdb/tui/tui-source.c:337 #1 0x00000000004f0538 in tui_show_frame_info (fi=0xd1d800) at /export/gnu/import/git/gdb/gdb/tui/tui-stack.c:351 #2 0x00000000004eb1bd in tui_selected_frame_level_changed_hook (level=0) at /export/gnu/import/git/gdb/gdb/tui/tui-hooks.c:226 #3 0x00000000006cd470 in select_frame (fi=0xd1d800) at /export/gnu/import/git/gdb/gdb/frame.c:1419 #4 0x00000000005c9850 in restore_selected_frame (a_frame_id=..., frame_level=0) at /export/gnu/import/git/gdb/gdb/thread.c:1038 #5 0x00000000005c9aa3 in do_restore_current_thread_cleanup (arg=0x57d82f0) at /export/gnu/import/git/gdb/gdb/thread.c:1106 #6 0x000000000055c3c0 in do_my_cleanups (pmy_chain=0xc11c50 <cleanup_chain>, old_chain=0x42ca0f0) at /export/gnu/import/git/gdb/gdb/cleanups.c:155 #7 0x000000000055c42d in do_cleanups (old_chain=0x42ca0f0) at /export/gnu/import/git/gdb/gdb/cleanups.c:177 #8 0x000000000053ecd9 in insert_breakpoint_locations () at /export/gnu/import/git/gdb/gdb/breakpoint.c:2891 #9 0x000000000053e7c0 in insert_breakpoints () at /export/gnu/import/git/gdb/gdb/breakpoint.c:2716 #10 0x00000000005b48f4 in proceed (addr=18446744073709551615, siggnal=GDB_SIGNAL_DEFAULT, step=1) at /export/gnu/import/git/gdb/gdb/infrun.c:2205 -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-08-17 20:08 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-17 20:08 hjl.tools at gmail dot com [this message] 2012-08-17 20:16 ` [Bug tui/14486] " hjl.tools at gmail dot com 2012-08-27 17:01 ` cvs-commit at gcc dot gnu.org 2012-08-27 17:44 ` hjl.tools at gmail dot com
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=bug-14486-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).