it's also when i compile sml code:

> polyc gc_bench.sml
Segmentation fault (core dumped)

> gdb -c poly.core /home/nick/polyml/bin/poly
...
(gdb) bt
#0  0x0000000800fea618 in _rtld_is_dlopened () from /libexec/ld-elf.so.1
#1  0x0000000800fe9e3a in _rtld_is_dlopened () from /libexec/ld-elf.so.1
#2  0x0000000800fe6ea0 in dlopen () from /libexec/ld-elf.so.1
#3  0x0000000801213a48 in pthread_exit () from /lib/libthr.so.3
#4  0x000000080121396b in pthread_exit () from /lib/libthr.so.3
#5  0x000000080120885d in pthread_create () from /lib/libthr.so.3
#6  0x0000000000000000 in ?? ()
(gdb)

2017-02-21 16:57 GMT+02:00 Kostirya <[email protected]>:
> I sometimes get Segmentation fault on pure SML code (without FFI).
> Feels it's after main function finished.
>
>
>> gdb -c a.out.core a.out
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "amd64-marcel-freebsd"...
> Core was generated by `a.out'.
> Program terminated with signal 11, Segmentation fault.
> Reading symbols from /lib/libthr.so.3...done.
> Loaded symbols for /lib/libthr.so.3
> Reading symbols from /lib/libm.so.5...done.
> Loaded symbols for /lib/libm.so.5
> Reading symbols from /usr/lib/libc++.so.1...done.
> Loaded symbols for /usr/lib/libc++.so.1
> Reading symbols from /lib/libcxxrt.so.1...done.
> Loaded symbols for /lib/libcxxrt.so.1
> Reading symbols from /lib/libgcc_s.so.1...done.
> Loaded symbols for /lib/libgcc_s.so.1
> Reading symbols from /lib/libc.so.7...done.
> Loaded symbols for /lib/libc.so.7
> Reading symbols from /libexec/ld-elf.so.1...done.
> Loaded symbols for /libexec/ld-elf.so.1
> #0  0x000000080067e618 in _rtld_is_dlopened () from /libexec/ld-elf.so.1
> [New Thread 802023800 (LWP 100475/<unknown>)]
> [New Thread 802023400 (LWP 100474/<unknown>)]
> [New Thread 801c07400 (LWP 100473/<unknown>)]
> [New Thread 801c07000 (LWP 100472/<unknown>)]
> [New Thread 801c06c00 (LWP 100471/<unknown>)]
> [New Thread 801c06800 (LWP 100470/<unknown>)]
> [New Thread 801c06400 (LWP 100112/<unknown>)]
> (gdb) bt
> #0  0x000000080067e618 in _rtld_is_dlopened () from /libexec/ld-elf.so.1
> #1  0x000000080067de3a in _rtld_is_dlopened () from /libexec/ld-elf.so.1
> #2  0x000000080067aea0 in dlopen () from /libexec/ld-elf.so.1
> #3  0x00000008008a7a48 in pthread_exit () from /lib/libthr.so.3
> #4  0x00000008008a796b in pthread_exit () from /lib/libthr.so.3
> #5  0x000000080089c85d in pthread_create () from /lib/libthr.so.3
> #6  0x0000000000000000 in ?? ()
> (gdb)
>
> 2017-02-21 14:48 GMT+02:00 David Matthews <[email protected]>:
>> The latest version, provisionally called 5.6.1, has had very little change
>> for several months.  I'm not aware of any show-stoppers so I think it would
>> be a good time to make a release.  Because there have been some major
>> changes I was planning to call it 5.7.  This is the last chance to do any
>> last tests before the release.
>>
>> David
>> _______________________________________________
>> polyml mailing list
>> [email protected]
>> http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
_______________________________________________
polyml mailing list
[email protected]
http://lists.inf.ed.ac.uk/mailman/listinfo/polyml

Reply via email to