Re: Broken MPIR 2.6.0 on Cygwin64

[Corinna Vinschen <corinna-cygwin@cygwin.com>]

On Jun 21 10:30, Corinna Vinschen wrote:
> On Jun 21 00:39, Jean-Pierre Flori wrote:
> > [...]
> > /bin/sh ../libtool --tag=CC    --mode=link gcc -std=gnu99  -m64 -O2
> > -march=corei7-avx -mtune=corei7-avx    -o t-bswap.exe t-bswap.o
> 
> Uhm, are you sure this arch and tune options aren't the problem here?
> 
> > Stack trace:
> > Frame        Function    Args
> > 00000C2A590  0000000003E (00000000000, 01300000001, 00100512180, 00000000000)
> > 00000C2A590  00100493B54 (00000000000, 006000F4B30, 00000000023, 00000000000)
> > 00000C2A650  00100433783 (00100534780, 00600057550, 001800C0C2C, 00000000000)
> > 00000000000  0010040E82C (00600022D10, 00600023CF8, 00100436389, 00000000000)
> > 00000000001  0010040F2E0 (001802DE300, 00600019870, 001800C0C2C, 00600017A30)
> > 001004DDD08  001004113FB (00100520580, 00000000000, 001802E3E9D, 001802DF658)
> > 001004DDD08  001004BF4C0 (00000C2A9B0, 00000C2AA46, 001801691B1, 00000000000)
> > 00000C2AB80  0018004836E (00000000000, 00000000000, 00000000000, 00000000000)
> > 00000000000  0018004618B (00000000000, 00000000000, 00000000000, 00000000000)
> > 00000000000  0018004634F (00000000000, 00000000000, 00000000000, 00000000000)
> > 00000000000  001004BDD31 (00000000000, 00000000000, 00000000000, 00000000000)
> > 00000000000  00100401010 (00000000000, 00000000000, 00000000000, 00000000000)
> > 00000000000  00076B7652D (00000000000, 00000000000, 00000000000, 00076BF9300)
> > 00000000000  0007726C521 (00000000000, 00000000000, 00000000000, 00076BF9300)
> > End of stack trace
> > }}}
> > 
> > * I have no problem building a shared lib, nor the test programs in
> > that case, but many (but not all) of them segfaults when they are run.
> > 
> > In the two above cases, I was not able to retrieve useful information
> > when attaching gdb to the segfaulting process.
> > I just saw that three threads were launched and the backtrace only
> > involved Cygwin/Windows dlls.
> 
> The function addresses on the top of the stack (starting with 0x0010...)
> are well within ld.  The Cygwin DLL seems to be involved only in so much
> as the application's (ld's) main routine has been called.

Btw., if you install the binutils-debuginfo package, you can also
evaluate the addresses within ld on the top of the stack:

$ addr2line -e /usr/lib/debug/usr/bin/ld.exe.dbg 00100493B54 00100433783 0010040E82C 0010040F2E0 001004113FB 001004BF4C0
/usr/src/debug/binutils-2.23.52-5/bfd/cofflink.c:219
/usr/src/debug/binutils-2.23.52-5/bfd/linker.c:1132
/usr/src/debug/binutils-2.23.52-5/ld/ldlang.c:2795
/usr/src/debug/binutils-2.23.52-5/ld/ldlang.c:3257
/usr/src/debug/binutils-2.23.52-5/ld/ldlang.c:6606
/usr/src/debug/binutils-2.23.52-5/ld/ldmain.c:415

But I admit this doesn;'t help a lot either, if you don't know why it
crashed at this point.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--
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