4 ms·
It's 100% reproducible. Just check out the previous to last commit on master on the github repo I linked to and run the tool with any command that invokes the n
by virtualritz 6y ago
It's 100% reproducible. Just check out the previous to last commit on master on the github repo I linked to and run the tool with any command that invokes the nsi crate.
Eg.:
> rdla dump foo.nsi
should produce the segfault before exiting the process.
Is there a jemallocator ticked where to attach a report for this?
- saagarjha 6y agoThanks! I think you found the jemallocator bug, so I'll try your project and follow up there.
- virtualritz 6y agoI think that bug may be fixed in jemalloc by now. The version of jemalloc that the jemalloc-sys crate tracks is from two years ago. I tried bumping jemalloc to latest master but that makes the jemalloc-sys build fail (trivially with a missing script but still). Also there is this: https://github.com/gnzlbg/jemallocator/issues/136 https://github.com/gnzlbg/jemallocator/issues/136