[Bug 219402] bsdgrep jemalloc assertion failure with --mmap
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri May 19 13:45:16 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219402
Bug ID: 219402
Summary: bsdgrep jemalloc assertion failure with --mmap
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: bin
Assignee: freebsd-bugs at FreeBSD.org
Reporter: emaste at freebsd.org
Running a test like that documented in 165471 resulted in an assertion failure:
nuc% cd /usr/share
nuc% time bsdgrep --mmap -r -e '^Feb' *
<jemalloc>: jemalloc_arena.c:353: Failed assertion: "p[i] == 0"
zsh: abort bsdgrep --mmap -r -e '^Feb' *
bsdgrep --mmap -r -e '^Feb' * 0.04s user 0.04s system 99% cpu 0.081 total
(lldb) bt
* thread #1, stop reason = signal SIGABRT
* frame #0: 0x000000015747cd8a libc.so.7`__sys_thr_kill + 10
frame #1: 0x000000015747cd54 libc.so.7`raise + 52
frame #2: 0x000000015747ccc9 libc.so.7`abort + 73
frame #3: 0x000000015747497f libc.so.7`___lldb_unnamed_symbol886$$libc.so.7
+ 447
frame #4: 0x000000015746d6f9 libc.so.7`___lldb_unnamed_symbol835$$libc.so.7
+ 233
frame #5: 0x000000015746d3b1 libc.so.7`___lldb_unnamed_symbol833$$libc.so.7
+ 353
frame #6: 0x000000015744f96d libc.so.7`___lldb_unnamed_symbol319$$libc.so.7
+ 397
frame #7: 0x0000000157477eba libc.so.7`___lldb_unnamed_symbol952$$libc.so.7
+ 202
frame #8: 0x000000015747871b libc.so.7`__realloc + 667
frame #9: bsdgrep`grep_realloc(ptr=<unavailable>, size=<unavailable>) at
util.c:542
frame #10: bsdgrep`grep_fgetln [inlined] grep_lnbufgrow at file.c:173
frame #11: bsdgrep`grep_fgetln(f=0x0000068da0c1c040,
lenp=0x00007fffffffe400) at file.c:213
frame #12: bsdgrep`procfile(fn="i18n/esdb/esdb.dir.db") at util.c:253
frame #13: bsdgrep`grep_tree(argv=<unavailable>) at util.c:182
frame #14: bsdgrep`main(argc=<unavailable>, argv=0x00007fff00000005) at
grep.c:776
frame #15: 0x000000000040226f bsdgrep`_start + 383
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list