Marking as done in 2.2. Hard to fix in 2.0 though :/
Andy
Hi,
On Tue 06 Jan 2015 15:27, Anthonin Bonnefoy
writes:
> Example program:
> ```
> #include
> #include
> #include
I had to add to this to get it to compile on 2.2. I
wonder if that's a problem? Anyway it segfaults directly on 2.2:
[Switching to Thread 0x744d1700 (LWP 8284)]
0x7f
Forget about the specific sha1, it compiled with my system-wide .so which
should be on the v2.0.11 tag.
I tried to reproduce the problem in a rr record (I had to change
SIG_SUSPEND to SIGUSR1 in bdwgc) without success.
On Thu, Jun 23, 2016 at 8:43 AM, Anthonin Bonnefoy <
anthonin.bonne...@securac
I moved guile to 08df681976d6c6d97a659f4aebb6f7125e5aad2e before generating
those coredumps.
Backtraces are a bit different between executions, so here are two "t a a
bt" from two differents coredump.
First backtrace:
#0 GC_generic_malloc (lb=524288, k=) at malloc.c:185
Thread 12 (Thread 0x7fb4
I can reproduce this bug, but I can't get backtraces from my core file
:/ Irritating. Are you able to get backtraces reliably? Can you
provide a "thr apply all bt" ?
Regards,
Andy
On Tue 06 Jan 2015 15:27, Anthonin Bonnefoy
writes:
> Hi all,
>
> I have segfaults occurring sometimes when th
Hi all,
I have segfaults occurring sometimes when threads are starting with
scm_with_guile while main thread is using malloc.
Example program:
```
#include
#include
#include
static void *a_libguile_thread(void *unused) {
}
static void *a_libguile_thread_(void *unused) {
scm_with_guile(a_
