public inbox for
help / color / mirror / Atom feed
* insight/225: Cygwin-gdb can't find linker symbol for virtual table
@ 2003-05-07 17:53 joshua.julin
  0 siblings, 0 replies; only message in thread
From: joshua.julin @ 2003-05-07 17:53 UTC (permalink / raw)
  To: insight-gnats

>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
>Originator:     jjulin
>Release:        GNU gdb 2003-03-03-cvs (cygwin-special)
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.
// There are 3 steps:
// step 1.  create this file:
class Object
    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. 


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2003-05-07 17:53 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-07 17:53 insight/225: Cygwin-gdb can't find linker symbol for virtual table joshua.julin

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).