On Mon, Jun 16, 2014 at 10:57, Stuart Henderson wrote: > #0 0x00001746a7f112b4 in strlen ( > str=0x1746a5b74ff8 "ÐÐÐÐÐÐÐÐ" <Address 0x1746a5b75000 out of > bounds>) > at /usr/src/lib/libc/string/strlen.c:39 > 39 for (s = str; *s; ++s) > (gdb) x/16x str > 0x1746a5b74ff8: 0xd0d0d0d0 0xd0d0d0d0 Cannot access memory at > address
> Backtrace from the other crashing run had the same functions, but the > crash trigger variables had freed (0xdf) rather than unallocated (0xd0) > memory e.g. > (gdb) x/x this->Config > 0x316fe402ff8: 0xdfdfdfdf So you are running with J as well? The first crash might go away without J, but the second will only go away now with little j. Of course, we don't want to do that. The first bug seems a little simpler. Based on the trace, cmTarget should initialize config to empty string, not just memory. Harder to tell where the free is in the second case.
