bug-libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libtool 2.2.11a] testsuite: 48 69 92 failed [cygwin]


From: Ralf Wildenhues
Subject: Re: [libtool 2.2.11a] testsuite: 48 69 92 failed [cygwin]
Date: Sat, 12 Jun 2010 10:58:12 +0200
User-agent: Mutt/1.5.20 (2009-10-28)

Hi Charles,

thanks for the report.

* Charles Wilson wrote on Fri, Jun 11, 2010 at 02:28:41PM CEST:
> In 48, the problem occurs during libtool --clean:
> /usr/src/packages/libtool/git/build/libtool: line 1693:
> sub3/subsub/sub3/subsub/.libs/m1_ltshwrapper: No such file or directory

This failure is probably easiest to debug and fix if you run
  make check-local TESTSUITEFLAGS='-v -d -x 48'
  cd tests/testsuite.dir/048

and rerun the failing mode=clean command with --debug as first libtool
argument.

> In 69, the library fails to open:

No idea.  Maybe having the error reporting from libltdl fixed may help
get a better clue here?

> In 92, there's a segfault:
> stderr:
> exceptions_in_prog
> caught: exception in program
> exceptions_in_lib
> caught inside lib: exception in library
> caught: exception from library
> exceptions_in_module
> caught inside module: exception in module
> caught: exception from module
> /usr/src/packages/libtool/git/build/tests/testsuite.dir/at-groups/92/test-source:
> line 399:  9032 Segmentation fault      (core dumped) $LIBTOOL
> --mode=execute -dlopen m/module.la "$lt_exe"
> stdout:
> ../../libtool/tests/exceptions.at:262: exit code was 139, expected 0

Hmm, this probably warrants a debugging session on Cygwin, i.e.,
something like
  ../../../libtool --mode=execute -dlopen m/module.la gdb ./main.exe
  run
  backtrace

in the test directory.

In order to find out whether this is a problem with uninstalled
libraries only, you can try commenting out the test in line 262 of
exceptions.at and rerunning test 92.

Thanks,
Ralf



reply via email to

[Prev in Thread] Current Thread [Next in Thread]