public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: craig@triscend.com To: insight-gnats@sources.redhat.com Subject: insight/159: Stack trace within register window Date: Thu, 23 May 2002 13:13:00 -0000 [thread overview] Message-ID: <20020523200840.15602.qmail@sources.redhat.com> (raw) >Number: 159 >Category: insight >Synopsis: Stack trace within register window >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu May 23 13:13:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: craig@triscend.com >Release: unknown-1.0 >Organization: >Environment: Windows 2K/Cygwin arm-elf-gdb >Description: A stack trace is displayed if a register is removed from the register window, and then an empty cell is clicked and then try to selecte display all registers. >How-To-Repeat: Start GDB and open the register window. Click on a register value and remove it from the display. Click on an empty cell (one that does not contain a register) and then selecte display all registers. >Fix: See the attached patch file, which also contains a fix for bug report 142. >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/plain; name="regwin.itb.pat" Content-Disposition: inline; filename="regwin.itb.pat" Index: regwin.itb =================================================================== RCS file: /cvs/src/src/gdb/gdbtk/library/regwin.itb,v retrieving revision 1.16 diff -c -p -r1.16 regwin.itb *** regwin.itb 16 May 2002 01:09:37 -0000 1.16 --- regwin.itb 23 May 2002 19:58:46 -0000 *************** body RegWin::_build_win {} { *** 225,231 **** -background [pref get gdb/font/highlight_bg] $itk_component(table) tag raise highlight $itk_component(table) tag configure sel \ ! -foreground [pref get gdb/font/select_fg] $itk_component(table) tag configure header \ -foreground [pref get gdb/font/header_fg] \ -background [pref get gdb/font/header_bg] \ --- 225,232 ---- -background [pref get gdb/font/highlight_bg] $itk_component(table) tag raise highlight $itk_component(table) tag configure sel \ ! -foreground [pref get gdb/font/select_fg] \ ! -background [pref get gdb/font/select_bg] $itk_component(table) tag configure header \ -foreground [pref get gdb/font/header_fg] \ -background [pref get gdb/font/header_bg] \ *************** body RegWin::_display_all {} { *** 715,721 **** if {[catch {$itk_component(table) index active} cell]} { set active {} } else { ! set active $_register($cell) } _layout_table if {$active != ""} { --- 716,724 ---- if {[catch {$itk_component(table) index active} cell]} { set active {} } else { ! if {[catch {set active $_register($cell)}]} { ! set active {} ! } } _layout_table if {$active != ""} {
reply other threads:[~2002-05-23 20:13 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020523200840.15602.qmail@sources.redhat.com \ --to=craig@triscend.com \ --cc=insight-gnats@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: 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).