Using OpenBSD which allows me to force memory reallocation when realloc is
called.
ln -s R /etc/malloc.conf
What steps will reproduce the problem?
1. Enable realloc
2. Start wmii using default wmiirc
3. If it starts, open a terminal
What is the expected result? What do you see instead?
Expected behave is to start up, parse the rc script and allow launching of the
terminal
Frequently it will SIGSEGV in regcomp.c at startup. If it is able to start up,
it will SIGSEGV in regexec.c when launching an application.
Something is lost when reallocation takes place. I assume, typically the OS
doesn't bother with the reallocation so there isn't usually a crash. Forcing
reallocation to occur every time exposes the bug.
What version of the product are you using (wmii -v)? On what operating
system (uname -a)?
OpenBSD 5.6 amd64
OpenBSD ports has version 3.6 which is where I discovered the problem, but it
is also reproducible in 3.9.2
Original issue reported on code.google.com by Tro...@gmail.com on 5 Nov 2014 at 4:43
Original issue reported on code.google.com by
Tro...@gmail.com
on 5 Nov 2014 at 4:43