http://bugzilla.gdcproject.org/show_bug.cgi?id=233
--- Comment #4 from Sebastien Alaiwan ---
Yes, it seems so.
(gdb) run
Starting program: /home/ace/projects/fuzzing/crashed/fuzzalloc
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_
http://bugzilla.gdcproject.org/show_bug.cgi?id=233
--- Comment #3 from Iain Buclaw ---
I can't reproduce it in master, which is using the next version of druntime
compared to what is shipped in Debian.
Is the segfault consistently in that location?
--
You are receiving this mail because:
You a
http://bugzilla.gdcproject.org/show_bug.cgi?id=233
--- Comment #2 from Sebastien Alaiwan ---
By the way, here's my version.
$ gdc --version
gdc (Debian 5.4.0-6) 5.4.0 20160609
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There i
http://bugzilla.gdcproject.org/show_bug.cgi?id=233
--- Comment #1 from Sebastien Alaiwan ---
Here's what I get in GDB:
Program received signal SIGSEGV, Segmentation fault.
__memset_sse2 () at ../sysdeps/x86_64/multiarch/../memset.S:80
80 ../sysdeps/x86_64/multiarch/../memset.S: No such file
http://bugzilla.gdcproject.org/show_bug.cgi?id=233
Bug ID: 233
Summary: crash in memory allocator
Product: GDC
Version: 5.x
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: High
