public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: "a.fink" <afink@sarance.com>
To: insight@sources.redhat.com
Subject: Insight on Cygwin : GUI is not showing up
Date: Thu, 29 Sep 2005 18:36:00 -0000	[thread overview]
Message-ID: <200509291835.j8TIZYoN006363@webmail3.megamailservers.com> (raw)

[-- 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,

             reply	other threads:[~2005-09-29 18:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29 18:36 a.fink [this message]
2005-09-29 19:08 ` Dave Murphy
2005-09-29 22:17   ` Accounts
2005-09-30 15:21     ` Dave Murphy

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=200509291835.j8TIZYoN006363@webmail3.megamailservers.com \
    --to=afink@sarance.com \
    --cc=insight@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: link
Be 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).