RE: building insight with mingw

["Dave Murphy" <wintermute2k4@ntlworld.com>]

> -----Original Message-----
> From: insight-owner@sources.redhat.com
> [mailto:insight-owner@sources.redhat.com]On Behalf Of Christopher Faylor
> Sent: 19 January 2004 21:03
> To: Keith Seitz
> Cc: Dave Murphy; insight@sources.redhat.com
> Subject: Re: building insight with mingw
>
>
> On Mon, Jan 19, 2004 at 10:37:06AM -0800, Keith Seitz wrote:
> >On Mon, 2004-01-19 at 10:25, Dave Murphy wrote:
> >> I'm currently trying to build gdb/insight under mingw. So far
> I've managed
> >> to get it to compile and install but not work as yet. Insight complains
> >> about invalid command name "ide_cygwin_path" - I've enabled this in
> >> tclwinpath.c but so far no joy. Is there anything else I need
> to do to get
> >> tcl to recognise this command?
> >
> >I wasn't aware that one could compile gdb under mingw. Oh well, shows
> >how out of touch I am...
>
> I don't think that gdb builds without unofficial patches that are
> sponsored by mingw folk.  If that is the case, then that makes building
> gdb/insight a problem for mingw since it isn't really a supported
> platform.
>

It would be nice if it was a supported platform though :)

I've managed to get past the ide_cygwin_path stuff now, everything compiles
and installs but Insight just stops for no readily apparent reason.
Attempting to debug gives me a SIGSEGV in mscvrt.dll relating to setjmp
which is confusing me a little.

Program received signal SIGSEGV, Segmentation fault.
0x7801ea8c in setjmp () from C:\WINNT\system32\msvcrt.dll
(gdb) backtrace
#0  0x7801ea8c in setjmp () from C:\WINNT\system32\msvcrt.dll
#1  0x0041fe6c in catcher (func=0x41fff0 <do_catch_errors>,
func_uiout=0x1279498,
    func_args=0x22d750, func_val=0x22d748, func_caught=0x22d74c,
errstring=0x5e90b7 "", mask=6)
    at ../../../insight-6.0.new/gdb/top.c:432
#2  0x00420046 in catch_errors (func=0x418e30 <wrapped_call>,
func_args=0x22d780,
    errstring=0x5e90b7 "", mask=6) at ../../../insight-6.0.new/gdb/top.c:514
#3  0x00418d62 in gdbtk_call_wrapper (clientData=0x419170, interp=0x1284510,
objc=2,
    objv=0x1287044) at
../../../insight-6.0.new/gdb/gdbtk/generic/gdbtk-cmds.c:356
#4  0x615ce62c in TclEvalObjvInternal (interp=0x2, objc=19427396, objv=0x1,
command=0x0, length=0,
    flags=2) at ../../../../insight-6.0.new/tcl/generic/tclBasic.c:3048
#5  0x01284510 in ?? ()
#6  0x00000002 in ?? ()
#7  0x01287044 in ?? ()
#8  0x00000001 in ?? ()

digging around I found this
http://sources.redhat.com/ml/gdb/2002-06/msg00135.html which suggests that
setjmp/longjmp should not be used. Currently I'm not sure if the error is
caused by setjmp or by something I've introduced at this point.

Any help in finding the problem would be greatly appreciated


Dave