Re: crashing socket tests

Bruno Haible <[email protected]>
Newsgroups gmane.lisp.clisp.devel
Message-ID <3355596.PGgX4mLpGk@omega>
Hi Vladimir,

> Besides this I observe weird behaviour with amd64 builds on linux - both
> single and multithreaded: without libffcall there is consistent segfault on
> sockets tests while with libffcall enabled everything works fine. Will
> investigate this further but any clue will be helpful.

I also observed segfaults on or soon after socket tests in various
configurations in February 2017. It seemed to depend on alignment options,
but tracking down this route it behaved like a Heisenbug.

A build with GC debugging enabled did not help.

I think to resolve this we need one of the following approaches:
  - Comment out some tests (the socket tests especially) and see if the
    testsuite still crashes occasionally.
  - Review the code of socket.d for ANY kind of mistake (usual GC-safety
    mistakes are not likely - see testing I mentioned above).
  - New kinds of debugging tools, in the spirit of GCC's "sanitizers" or
    valgrind.

Bruno


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.