Re: Problem running ddd on Cygwin

[Andrew Gaylard]

address@hidden wrote:

> Program received signal SIGSEGV, Segmentation fault.
> 0x01468c87 in XtDisplay () from /usr/X11R6/bin/cygXt-6.dll
>
> (gdb) backtrace
> #0  0x01468c87 in XtDisplay () from /usr/X11R6/bin/cygXt-6.dll
> #1  0x00507ded in string_app_value(string const&, char const*, bool) (
>     address@hidden, v=0x50a252 "3.3.8", check_default=false) at 
> options.C:2059
> #2  0x0050b6ca in save_options(unsigned long) (flags=1024) at 
> strclass.h:964
> #3  0x004b88ac in ddd_cleanup() () at exit.C:170
> #4  0x004ba474 in ddd_xt_error(char*) (message=0x0) at exit.C:674
> #5  0x004ba347 in ddd_xt_error(char*) (
>     message=0x10072f70 "attempt to add non-widget child 
> \"DropSiteManager\" to parent \"ddd\" which supports only widgets") at 
> exit.C:689
> #6  0x0145f1db in XtError () from /usr/X11R6/bin/cygXt-6.dll
> #7  0x0145ecb7 in DefaultMsg () from /usr/X11R6/bin/cygXt-6.dll
> #8  0x0145ed34 in _XtDefaultErrorMsg () from /usr/X11R6/bin/cygXt-6.dll
> #9  0x0145ee3e in XtAppErrorMsg () from /usr/X11R6/bin/cygXt-6.dll
> #10 0x0145b9c7 in _XtCreateWidget () from /usr/X11R6/bin/cygXt-6.dll
> #11 0x0145bb25 in XtCreateWidget () from /usr/X11R6/bin/cygXt-6.dll
> #12 0x006ca6b6 in _XmGetDropSiteManagerObject ()
>     at /usr/include/c++/3.2/iostream:62
> #13 0x006d3002 in _XmDropSiteWrapperCandidate ()
>     at /usr/include/c++/3.2/iostream:62
> #14 0x00647796 in ResizeWrapper () at /usr/include/c++/3.2/iostream:62
> #15 0x00646869 in ResizeWrapper4 () at /usr/include/c++/3.2/iostream:62
> #16 0x00689266 in initialize () at /usr/include/c++/3.2/iostream:62
> #17 0x0145ad67 in CallInitialize () from /usr/X11R6/bin/cygXt-6.dll
> #18 0x0145ad30 in CallInitialize () from /usr/X11R6/bin/cygXt-6.dll
> #19 0x0145b351 in xtCreate () from /usr/X11R6/bin/cygXt-6.dll
> #20 0x0022f590 in ?? ()
> #21 0x1006a0d8 in ?? ()
> #22 0x0022fd10 in ?? ()
> (gdb) continue

Dirk,

This backtrace has some problems:  there's no way the _Xm functions
are in /usr/include/c++/3.2/iostream!  So either your stack's scrambled,
or the optimisation has left out some frame information.

Can you try rebuilding ddd without -O2, just with -g?

Then try to get the problem to happen again, and let's see if *that*
backtrace is any better.

Andrew.