Re: insight crashed under cygwin

[Joerg Rapka <joerg.rapka@duagon.com>]

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
>