public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
* Insight on Cygwin : GUI is not showing up
@ 2005-09-29 18:36 a.fink
  2005-09-29 19:08 ` Dave Murphy
  0 siblings, 1 reply; 4+ messages in thread
From: a.fink @ 2005-09-29 18:36 UTC (permalink / raw)
  To: insight

[-- Attachment #1: Type: text/plain, Size: 1893 bytes --]

Hi

I'm trying to build and run Insight-6.1 on Cygwin/X, on a Windows XP SP2 host.

The underlying gdb is configured for mips-elf target.
Everything seems to build nicely, but when I run gdb, only the usual command-line
gdb is showing up, with nothing from Insight.

Here's the steps I've followed :

download ftp://sources.redhat.com/pub/gdb/releases/insight-6.1.tar.gz
download a patch for the included tcl libraries (forgot from where, so I've
attached the patch file "cyg-tcl-sehfix.diff")

$> cp ~/insight-6.1.tar.gz /usr/src/archives
$> cd /usr/src
$> tar -xzvf ./archives/insight-6.1.tar.gz
$> cp ~/cyg-tcl-sehfix.diff /usr/src/insight-6.1
$> cd /usr/src/insight-6.1/tcl/win
$> patch -p 2 < ../../cyg-tcl-sehfix.diff
$> cd /usr/src/insight-6.1
$> ./configure --target=mips-elf
$> make
$> make install

So far so good, no error or warning showed up.
Then I launch gdb, but there's not GUI / popup windows from Insight that appear.

Any idea what could be wrong ?
I've followed the instructions from "http://sources.redhat.com/insight/README",
which say that 'if everything went well', the GUI should show up.

I'm not too sure about this part of the above README :
"Just run it like you would a normal GDB (in fact, it's actually called `gdb').
If everything goes well, you should have several windows pop up."

Shouldn't it be the other way around ? I'm thinking, normally it should be the
above layer (insight) that calls gdb, or not the other way around, unless the
insight build adds something to the gdb source so that is calls the Inishgt
tcl/tk GUI when launched..

Any hint ?

I have had major failures with ddd, and now with Insight, and people around me
are waiting for these tools.
Here's a good example of OSS not being the good choice for anyone :/

Thanks for any bits of help !!!
--
Antoine Fink
MITEL NETWORKS
350 Legget Drive
Kanata, ON K2K 2W7
Antoine_Fink@Mitel.com



[-- Attachment #2: cygtclsehfix.diff --]
[-- Type: application/octet-stream, Size: 2445 bytes --]

Index: tcl/win/tclWin32Dll.c
===================================================================
RCS file: /cvs/src/src/tcl/win/tclWin32Dll.c,v
retrieving revision 1.9
diff -p -u -r1.9 tclWin32Dll.c
--- tcl/win/tclWin32Dll.c	21 Jan 2003 19:40:22 -0000	1.9
+++ tcl/win/tclWin32Dll.c	26 Jul 2005 15:55:47 -0000
@@ -38,8 +38,8 @@ static HINSTANCE hInstance;	/* HINSTANCE
 static int platformId;		/* Running under NT, or 95/98? */
 
 #ifdef HAVE_NO_SEH
-static void *ESP;
-static void *EBP;
+static void *ESP __attribute__ ((used));
+static void *EBP __attribute__ ((used));
 #endif /* HAVE_NO_SEH */
 
 /*
@@ -393,7 +393,7 @@ TclpCheckStackSpace()
 }
 #ifdef HAVE_NO_SEH
 static
-__attribute__ ((cdecl))
+__attribute__ ((cdecl)) __attribute__ ((used))
 EXCEPTION_DISPOSITION
 _except_checkstackspace_handler(
     struct _EXCEPTION_RECORD *ExceptionRecord,
Index: tcl/win/tclWinChan.c
===================================================================
RCS file: /cvs/src/src/tcl/win/tclWinChan.c,v
retrieving revision 1.5
diff -p -u -r1.5 tclWinChan.c
--- tcl/win/tclWinChan.c	21 Jan 2003 19:40:22 -0000	1.5
+++ tcl/win/tclWinChan.c	26 Jul 2005 15:55:47 -0000
@@ -122,8 +122,8 @@ static Tcl_ChannelType fileChannelType =
 };
 
 #ifdef HAVE_NO_SEH
-static void *ESP;
-static void *EBP;
+static void *ESP __attribute__ ((used));
+static void *EBP __attribute__ ((used));
 #endif /* HAVE_NO_SEH */
 
 \f
@@ -1106,7 +1106,7 @@ Tcl_MakeFileChannel(rawHandle, mode)
 }
 #ifdef HAVE_NO_SEH
 static
-__attribute__ ((cdecl))
+__attribute__ ((cdecl)) __attribute__ ((used))
 EXCEPTION_DISPOSITION
 _except_makefilechannel_handler(
     struct _EXCEPTION_RECORD *ExceptionRecord,
Index: tcl/win/tclWinFCmd.c
===================================================================
RCS file: /cvs/src/src/tcl/win/tclWinFCmd.c,v
retrieving revision 1.6
diff -p -u -r1.6 tclWinFCmd.c
--- tcl/win/tclWinFCmd.c	7 Feb 2003 19:52:00 -0000	1.6
+++ tcl/win/tclWinFCmd.c	26 Jul 2005 15:55:47 -0000
@@ -469,7 +469,7 @@ DoRenameFile(
 }
 #ifdef HAVE_NO_SEH
 static
-__attribute__ ((cdecl))
+__attribute__ ((cdecl)) __attribute__ ((used))
 EXCEPTION_DISPOSITION
 _except_dorenamefile_handler(
     struct _EXCEPTION_RECORD *ExceptionRecord,
@@ -651,7 +651,7 @@ DoCopyFile(
 }
 #ifdef HAVE_NO_SEH
 static
-__attribute__ ((cdecl))
+__attribute__ ((cdecl)) __attribute__ ((used))
 EXCEPTION_DISPOSITION
 _except_docopyfile_handler(
     struct _EXCEPTION_RECORD *ExceptionRecord,

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Insight on Cygwin : GUI is not showing up
  2005-09-29 18:36 Insight on Cygwin : GUI is not showing up a.fink
@ 2005-09-29 19:08 ` Dave Murphy
  2005-09-29 22:17   ` Accounts
  0 siblings, 1 reply; 4+ messages in thread
From: Dave Murphy @ 2005-09-29 19:08 UTC (permalink / raw)
  To: afink; +Cc: insight

a.fink wrote:

>Hi
>
>I'm trying to build and run Insight-6.1 on Cygwin/X, on a Windows XP SP2 host.
>
>
>$> cp ~/insight-6.1.tar.gz /usr/src/archives
>$> cd /usr/src
>$> tar -xzvf ./archives/insight-6.1.tar.gz
>$> cp ~/cyg-tcl-sehfix.diff /usr/src/insight-6.1
>$> cd /usr/src/insight-6.1/tcl/win
>$> patch -p 2 < ../../cyg-tcl-sehfix.diff
>$> cd /usr/src/insight-6.1
>$> ./configure --target=mips-elf
>$> make
>$> make install
>
>  
>
you need to add --enable-gdbtk when configuring, you should then get 3 
binaries (assuming everything went well) insight (gui), gdb (cli)and 
gdbtui(curses interface)

>I have had major failures with ddd, and now with Insight, and people around me
>are waiting for these tools.
>Here's a good example of OSS not being the good choice for anyone :/
>  
>
Sometimes it just takes a little perseverance. I've recently managed to 
successfully built insight 6.1 with gdb 6.3 patched in for native 
windows host and arm-elf target using msys/mingw. The latest gdb from 
CVS head now builds with this enviroment with minimal patching - still 
having a bit of trouble convincing it to add Insight but I'll get there 
in the end.

Dave

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Insight on Cygwin : GUI is not showing up
  2005-09-29 19:08 ` Dave Murphy
@ 2005-09-29 22:17   ` Accounts
  2005-09-30 15:21     ` Dave Murphy
  0 siblings, 1 reply; 4+ messages in thread
From: Accounts @ 2005-09-29 22:17 UTC (permalink / raw)
  To: Dave Murphy; +Cc: insight

Hi Dave,

You do know that Insight is still in the GDB CVS Tree dont you?

Also, the Insight website has some recent CVS Snapshots, which should 
build OK.

That might be a lot easier than trying to take the insight code from 6.1 
and inject it onto GDB6.3 (without insight).  There have been a number 
of patches since then (just no official release).

Steven.

Dave Murphy wrote:

> a.fink wrote:
>
>> Hi
>>
>> I'm trying to build and run Insight-6.1 on Cygwin/X, on a Windows XP 
>> SP2 host.
>>
>>
>> $> cp ~/insight-6.1.tar.gz /usr/src/archives
>> $> cd /usr/src
>> $> tar -xzvf ./archives/insight-6.1.tar.gz
>> $> cp ~/cyg-tcl-sehfix.diff /usr/src/insight-6.1
>> $> cd /usr/src/insight-6.1/tcl/win
>> $> patch -p 2 < ../../cyg-tcl-sehfix.diff
>> $> cd /usr/src/insight-6.1
>> $> ./configure --target=mips-elf
>> $> make
>> $> make install
>>
>>  
>>
> you need to add --enable-gdbtk when configuring, you should then get 3 
> binaries (assuming everything went well) insight (gui), gdb (cli)and 
> gdbtui(curses interface)
>
>> I have had major failures with ddd, and now with Insight, and people 
>> around me
>> are waiting for these tools.
>> Here's a good example of OSS not being the good choice for anyone :/
>>  
>>
> Sometimes it just takes a little perseverance. I've recently managed 
> to successfully built insight 6.1 with gdb 6.3 patched in for native 
> windows host and arm-elf target using msys/mingw. The latest gdb from 
> CVS head now builds with this enviroment with minimal patching - still 
> having a bit of trouble convincing it to add Insight but I'll get 
> there in the end.
>
> Dave
>
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Insight on Cygwin : GUI is not showing up
  2005-09-29 22:17   ` Accounts
@ 2005-09-30 15:21     ` Dave Murphy
  0 siblings, 0 replies; 4+ messages in thread
From: Dave Murphy @ 2005-09-30 15:21 UTC (permalink / raw)
  To: insight

Accounts wrote:

> Hi Dave,
>
> You do know that Insight is still in the GDB CVS Tree dont you?


yep :)

> Also, the Insight website has some recent CVS Snapshots, which should 
> build OK.


Unfortunately CVS head doesn't currently build under msys/mingw. I've
got plain vanilla gdb to build with minimal patching but adding Insight
is still a little problematic, not far off though. I just need to figure
out why the gdbtk module isn't picking up the tcl headers and I think it
should be plain sailing from there.

> That might be a lot easier than trying to take the insight code from 
> 6.1 and inject it onto GDB6.3 (without insight).  There have been a 
> number of patches since then (just no official release).
>
I actually did this the other way round, injecting gdb 6.3 into the
Insight 6.1 tree, it's fairly easy to do although the patches aren't
exactly trivial. It was really just a matter of checking out the 6.1
tree, bringing the gdb sections up to 6.3 then applying a patch
generated from the mingw gdb source, Andrew's SEH fix and a couple of
minor configury changes.

Dave


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2005-09-30 15:21 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-09-29 18:36 Insight on Cygwin : GUI is not showing up a.fink
2005-09-29 19:08 ` Dave Murphy
2005-09-29 22:17   ` Accounts
2005-09-30 15:21     ` Dave Murphy

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