public inbox for insight-prs@sourceware.org help / color / mirror / Atom feed
From: joshua.julin@lmco.com To: insight-gnats@sources.redhat.com Subject: insight/225: Cygwin-gdb can't find linker symbol for virtual table Date: Wed, 07 May 2003 17:53:00 -0000 [thread overview] Message-ID: <20030507175021.18993.qmail@sources.redhat.com> (raw) >Number: 225 >Category: insight >Synopsis: Cygwin-gdb can't find linker symbol for virtual table >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed May 07 17:53:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: jjulin >Release: GNU gdb 2003-03-03-cvs (cygwin-special) >Organization: >Environment: cygwin >Description: Many useless and annoying dialog boxes appear when using the watch window to debug member variables of a class which contain a virtual destructor. Each dialog box says "can't find linker symbol for virtual table". I've only been able to replicate this problem on cygwin! This does not happen on linux boxes, but every cygwin box I've used duplicates this error. This points to an error in the cygwin-gdb code (I've already posted to the cygwin board), but insight handles this so poorly I thought I'd post to this board as well. See the How-to-repeat section. It's really easy to duplicate on cygwin. >How-To-Repeat: // There are 3 steps: // step 1. create this file: class Object { public: int x,y,z; double a,b,c; virtual ~Object() { } }; int main() { Object * obj = new Object; } //step 2. on cygwin, build using: g++ -g -o josh josh.cpp //step 3. on cygwin, run insight open the "watch window". // view Object's member variables. A ton of dialog // boxes should spew at you. // >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-05-07 17: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=20030507175021.18993.qmail@sources.redhat.com \ --to=joshua.julin@lmco.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).