public inbox for
 help / color / mirror / Atom feed
From: Pavel Fedin <>
To: 'Pavel Fedin' <>, 'Keith Seitz' <>
Subject: RE: Building Insight for Cygwin
Date: Thu, 01 Aug 2013 09:04:00 -0000	[thread overview]
Message-ID: <001601ce8e96$16b82ad0$44288070$> (raw)
In-Reply-To: <002601ce8db2$6bb2ad10$43180730$>


>  Additionally i do it on 64-bit Cygwin. Had to apply some patchwork,
> currently it almost builds. I will report results.

 I have built somewhat runable version, but it crashes:
--- cut ---
(gdb) run
Starting program: /usr/local/bin/arm-linux-gnueabi-insight
[New Thread 2292.0x1efc]
[New Thread 2292.0x1be8]
[New Thread 2292.0x14e0]

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) where
#0  0x0000000000000000 in ?? ()
#1  0x0000000468466239 in InitWindowClass
(titlebaricon=titlebaricon@entry=0x0) at tkWinWm.c:848
#2  0x00000004684691f7 in InitWm () at tkWinWm.c:895
#3  TkWmMapWindow (winPtr=0x600273aa0) at tkWinWm.c:2095
#4  0x00000004684ee69f in Tk_MapWindow (tkwin=0x600273aa0) at
#5  0x00000004684a3820 in MapFrame (clientData=0x60029cc00) at
#6  0x0000000000f91709 in TclServiceIdle () at ./../generic/tclTimer.c:704
--- cut ---

 Sorry but i have neither time nor intention to deal with this further. For
now i'll continue to use MinGW version.
 I think if this is interesting task, we should work with upgraded TCL/TK.
Currently it needs patching even for 64-bit MinGW.

 P.S. Yes, i remember that i can use standalone TCL/TK for Windows. But -
it's inconvenient to have dependency on some 3rd party DLLs, this worsens
software's portability.

Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia

      reply	other threads:[~2013-08-01  9:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29  9:40 Pavel Fedin
2013-07-30 23:21 ` Keith Seitz
2013-07-31  5:54   ` Pavel Fedin
2013-08-01  9:04     ` Pavel Fedin [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001601ce8e96$16b82ad0$44288070$' \ \ \ \

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