This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: sigsegv in compiled cygwin
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 4 Feb 2011 10:01:18 -0500
- Subject: Re: sigsegv in compiled cygwin
- References: <iigs04$cui$1@dough.gmane.org>
- Reply-to: cygwin at cygwin dot com
On Fri, Feb 04, 2011 at 09:40:46PM +0900, jojelino wrote:
>i'm trying to build cygwin with gcc 4.6 trunk. and compile succeed.
>but when i try to run cygwin-linked executables with new-compiled-one,
>initialization routine failed with sigsegv at win32_whatever+14
>
> 0x61171a20 <+0>: jmp 0x61171a25 <win32_GetKeyboardLayout@4+5>
> 0x61171a25 <+5>: mov 0x61171a2c,%eax
> 0x61171a2a <+10>: call *(%eax)
> 0x61171a2c <+12>: sbb %al,%al
>=> 0x61171a2e <+14>: pop %ss
>
>it seems redirection statement('Kludge alert') in autoload.cc didn't
>work as expected.
>what would i do??
Well, since you're trying to do something cutting edge and unsupported
it seems like you will have to debug the problem using gdb and, if you
really want this to work, make a change to autoload.cc to fix the
problem. Look at a call frame for normal program and find where
the return address is stored.
Either that or wait for us to move to a newer version of gcc.
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple