insight crashed under cygwin

insight crashed under cygwin

[Jörg Rapka]

Hello

I'm using the following configuration:
- Windows 2000
- latest release of cygwin 1.3.18-1
- insight-5.1 configured for target "arm-ecos-elf"

The compilation goes well (I have also tried insight-5.2.1 and 
insight-5.3 using Tcl/Tk 8.0.3; as described at 
http://sources.redhat.com/insight/cygwin.html).

If I run the application "arm-ecos-elf-gdb.exe" it crashed and I got a 
Windows containing an error message like this:
The application cannot be initialised (0xc0000022). Press "OK" to stop 
the application".

Some times ago I have used cygwin release 1.3.14-1. Compilation of 
insight goes well and the application works fine.

What's wrong with cygwin 1.3.18-1?

Best regards,
Joerg

Re: insight crashed under cygwin

[Keith Seitz]

On Fri, 2003-01-10 at 06:38, Jörg Rapka wrote:

> If I run the application "arm-ecos-elf-gdb.exe" it crashed and I got a 
> Windows containing an error message like this:
> The application cannot be initialised (0xc0000022). Press "OK" to stop 
> the application".

Where does it crash? Stack backtrace? (Run insight under gdb...)

Keith

Re: insight crashed under cygwin

[Joerg Rapka]

Hello

I have tried to used the debugger to debug the application 
"arm-ecos-elf-insight.exe". I got the following warning message from GDB:
Program received signal SIGSEV, segmentation fault (I cannot get the 
position where it crash neither perform a stack backtrace).
The same happens to all other "EXE" generated by the build process of 
insight (e.g. arm-ecos-elf-gdb.exe, cygitclsh30.exe, tix4180.exe, etc.).

I have donwloaded once again a new cygwin installation from the net, but 
always got the same result (NOTE: compiling of a cross GDB only works well).

Any tips?

Best regards,
Joerg


Keith Seitz schrieb:
> On Fri, 2003-01-10 at 06:38, Jörg Rapka wrote:
> 
> 
>>If I run the application "arm-ecos-elf-gdb.exe" it crashed and I got a 
>>Windows containing an error message like this:
>>The application cannot be initialised (0xc0000022). Press "OK" to stop 
>>the application".
> 
> 
> Where does it crash? Stack backtrace? (Run insight under gdb...)
> 
> Keith
> 

Re: insight crashed under cygwin

[Keith Seitz]

On Thu, 2003-01-16 at 02:02, Joerg Rapka wrote:

> I have tried to used the debugger to debug the application 
> "arm-ecos-elf-insight.exe". I got the following warning message from GDB:
> Program received signal SIGSEV, segmentation fault (I cannot get the 
> position where it crash neither perform a stack backtrace).
> The same happens to all other "EXE" generated by the build process of 
> insight (e.g. arm-ecos-elf-gdb.exe, cygitclsh30.exe, tix4180.exe, etc.).

Are you saying the backtrace is worthless (ie., corrupted stack)? Then
the only other thing that I can think of doing is running one of these
executables under strace. Can your build environment build a simple,
"Hello, world" executable that runs (using same compiler, linker, etc
that's used to build insight et al)?

Keith

Re: insight crashed under cygwin

[Joerg Rapka]

Hello

I load the application "arm-ecos-elf-insight.exe" into cygwin GDB and I 
got immediately the GDB warning message:
Program received signal SIGSEV, segmentation fault.
Then neither registers can be read nor a stack backtrace is possible (no 
stack available).
The same happens to all other "EXE" generated by the build process of
insight (e.g. arm-ecos-elf-gdb.exe, cygitclsh30.exe, tix4180.exe, etc.).
NOTE:
I'm able to have a successful build of cross tools binutils, gcc, 
gdb-only for target "arm-ecos-elf". Only cross build of insight fails.

Any special requirements for building any cross "insight" under cygwin?

Best regards,
Joerg


Keith Seitz wrote:
> On Thu, 2003-01-16 at 02:02, Joerg Rapka wrote:
> 
> 
>>I have tried to used the debugger to debug the application 
>>"arm-ecos-elf-insight.exe". I got the following warning message from GDB:
>>Program received signal SIGSEV, segmentation fault (I cannot get the 
>>position where it crash neither perform a stack backtrace).
>>The same happens to all other "EXE" generated by the build process of 
>>insight (e.g. arm-ecos-elf-gdb.exe, cygitclsh30.exe, tix4180.exe, etc.).
> 
> 
> Are you saying the backtrace is worthless (ie., corrupted stack)? Then
> the only other thing that I can think of doing is running one of these
> executables under strace. Can your build environment build a simple,
> "Hello, world" executable that runs (using same compiler, linker, etc
> that's used to build insight et al)?
> 
> Keith
> 

Re: insight crashed under cygwin

[Keith Seitz]

On Thu, 2003-01-16 at 23:29, Joerg Rapka wrote:
> I'm able to have a successful build of cross tools binutils, gcc, 
> gdb-only for target "arm-ecos-elf". Only cross build of insight fails.
> 
> Any special requirements for building any cross "insight" under cygwin?

None that I am aware of. What does "head config.status" say in the top
of your build directory? What version of the sources are you using? 5.1?
5.2? 5.3? CVS HEAD?

Keith

Re: insight crashed under cygwin

[Joerg Rapka]

Keith Seitz wrote:
> On Thu, 2003-01-16 at 23:29, Joerg Rapka wrote:
> 
>>I'm able to have a successful build of cross tools binutils, gcc, 
>>gdb-only for target "arm-ecos-elf". Only cross build of insight fails.
>>
>>Any special requirements for building any cross "insight" under cygwin?
> 
> 
> None that I am aware of. What does "head config.status" say in the top
> of your build directory? What version of the sources are you using? 5.1?
> 5.2? 5.3? CVS HEAD?
> 
> Keith
> 

content of file "config.status":
#!/bin/sh
# This file was generated automatically by configure.  Do not edit.
# This directory was configured as follows:
/src/gdb/insight-5.1/configure --host=i686-pc-cygwin 
--target=arm-ecos-elf --prefix=/tools/arm 
--exec-prefix=/tools/arm/H-i686-pc-cygwin -v --norecursion
# using "mh-frag"

NOTE:
I used this line to configure insight:
/src/gdb/insight-5.1/configure --host=i686-pc-cygwin 
--target=arm-ecos-elf --prefix=/tools/arm 
--exec-prefix=/tools/arm/H-i686-pc-cygwin -v

I'm using sources of insight release 5.1.

Best regards,
Joerg

Re: insight crashed under cygwin

[Keith Seitz]

On Fri, 2003-01-17 at 07:23, Joerg Rapka wrote:

> content of file "config.status":
> #!/bin/sh
> # This file was generated automatically by configure.  Do not edit.
> # This directory was configured as follows:
> /src/gdb/insight-5.1/configure --host=i686-pc-cygwin 
> --target=arm-ecos-elf --prefix=/tools/arm 
> --exec-prefix=/tools/arm/H-i686-pc-cygwin -v --norecursion
> # using "mh-frag"

Ok, well, that looks correct. (Darn! No smoking gun there!)

The only two other things I can think to try: update to 5.2 or 5.3 (see
caveats about windows problems -- workarounds in mailing list) or run
strace on insight and see where it is segfaulting.

Keith

Re: insight crashed under cygwin

[Joerg Rapka]

Keith Seitz wrote:
> On Fri, 2003-01-17 at 07:23, Joerg Rapka wrote:
> 
> 
>>content of file "config.status":
>>#!/bin/sh
>># This file was generated automatically by configure.  Do not edit.
>># This directory was configured as follows:
>>/src/gdb/insight-5.1/configure --host=i686-pc-cygwin 
>>--target=arm-ecos-elf --prefix=/tools/arm 
>>--exec-prefix=/tools/arm/H-i686-pc-cygwin -v --norecursion
>># using "mh-frag"
> 
> 
> Ok, well, that looks correct. (Darn! No smoking gun there!)
> 
> The only two other things I can think to try: update to 5.2 or 5.3 (see
> caveats about windows problems -- workarounds in mailing list) or run
> strace on insight and see where it is segfaulting.
> 
> Keith
> 

I have tried also 5.2 and 5.3 with the same result.
(taking care of http://sources.redhat.com/insight/cygwin.html).

I have tried to run strace on my insight, but it fails with the same 
SEGFAULT message.

Joerg

Re: insight crashed under cygwin

[Keith Seitz]

On Fri, 2003-01-17 at 07:49, Joerg Rapka wrote:

> I have tried to run strace on my insight, but it fails with the same 
> SEGFAULT message.
> 

strace dies? That's odd. What does "cygcheck -s -v -h -r" show?

Keith