This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
Re: insight on windows
- From: Keith Seitz <keiths at redhat dot com>
- To: vadiraj_kulkarni at lycos dot com
- Cc: "insight at sources dot redhat dot com" <insight at sources dot redhat dot com>
- Date: 03 Jun 2003 07:05:18 -0700
- Subject: Re: insight on windows
- Organization:
- References: <BFDOEEDAEGGJKDAA@mailcity.com>
On Mon, 2003-06-02 at 22:25, vadraj kulkarni wrote:
> Ans: i have used gcc - 3.2 for compiling insight -5.0
Should work, but since 5.0 is about three (four?) years old, I haven't
tried it in a very, very long time.
> >Run the exe under gdb (gdb -nw). Then when the exe crashes, get a
> >backtrace using the "backtrace" command. Send the stack backtrace to the
> >list.
> >
> Ans: Unfortunately i am not finding any backtrace command. I have already tried gdb -nw(ie. arm-elf-gdb -nw)
> Same error message i will get. Case is true with gdb -v(arm-elf-gdb -v) also.
The gdb that came with cygwin doesn't work? You should be able to do:
$ /usr/bin/gdb -nx -q gdb
(gdb) run -w
[wait for crash]
(gdb) backtrace
Perl crashing during configure time (as you posted on cygwin mailing
list) sounds suspicious (like a cygwin.dll problem -- multiples?).
Please send the file "cygcheck.out" from "cygcheck -s -v -r >
cygcheck.out".
Methinks your cygwin installation is messed up.
Keith