public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: ching@coware.com To: insight-gnats@sources.redhat.com Subject: insight/226: core dump when cursor move over class member function without debugger info. Date: Wed, 07 May 2003 22:53:00 -0000 [thread overview] Message-ID: <20030507224951.22882.qmail@sources.redhat.com> (raw) >Number: 226 >Category: insight >Synopsis: core dump when cursor move over class member function without debugger info. >Confidential: no >Severity: serious >Priority: high >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed May 07 22:53:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: ching@coware.com >Release: unknown-1.0 >Organization: >Environment: Linux 7.3 and Solaris. >Description: insight 5.2 crashed when the cursor moves over a class member function that did not compile with debugger information. Platform: Redhat 7.3 Linux scooby 2.4.18-3 #1 Thu Apr 18 07:37:53 EDT 2002 i686 unknown Here is of my observation. It looks like the problem is caused by tk_command_loop() cannot not re-entry. So what happens is when the error occurs in gdb/cp-valprint.c 123 } 124 error ("invalid pointer to member function"); 125 } which caused a siglongjump to gdb/top.c 421 caught = SIGSETJMP (catch); 422 if (!caught) 423 val = (*func) (func_uiout, func_args); after that it will call tk_command_loop() in gdb/gdbtk/generic/gdbtk-hooks.c to re-enter the Tk_MainLoop. Since it is the same gdbtk_interp tcl interpeter and it keeps evaluation the same tcl_command and finially the stack is screwed up. >How-To-Repeat: To reproduce: 1. unzip the carsh.bz2 file. 2. cd crash 3. invoke insight 4. file t 5. b t.cpp:60 6. run 7. move cusor over line 60 of "data_valid.read()" after that you will see dozen of the following messages. invalid pointer to member function 8. enter c to continue debugging 9. Segmentation fault (core dumped) >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-05-07 22:53 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=20030507224951.22882.qmail@sources.redhat.com \ --to=ching@coware.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).