Open GoogleCodeExporter opened 8 years ago
Thanks for the bug report.
Would you be able to compile in debug mode (./configure --enable-debug=yes
...), reinstall and attach gdb to the daemon until it crashes ? We could then
get a backtrace with gdb's "thread apply all bt" command.
Original comment by fabrice....@gmail.com
on 12 Sep 2012 at 5:48
[deleted comment]
Here you go. Hope this helps you track down the issue.
Original comment by martin.schumann
on 12 Sep 2012 at 7:03
Attachments:
I've just noticed that v1.01 is already released and tried it. But the result
stayed the same. I've also done a backtrace (which looks quite similar I guess).
Original comment by martin.schumann
on 12 Sep 2012 at 7:29
Attachments:
What version of boost do you have ?
Could you try rebuilding with "./configure ... --enable-mempool=no" ?
Original comment by fabrice....@gmail.com
on 12 Sep 2012 at 7:41
I've got boost 1.50.0.
The mempool option seems to have done the trick. At least pinot-dbus-daemon
does not crash after creating the 3rd thread anymore. I'll have pinot index my
files and report if it segfaulted again.
Original comment by martin.schumann
on 12 Sep 2012 at 8:02
Looks good so far. No crash in the last 30 minutes indexing. Should I suggest
the ArchLinux pacakage maintainer adding --enable-mempool=no ?
Original comment by martin.schumann
on 12 Sep 2012 at 8:53
Yes, good idea. With boost >= 1.48, that's what I would recommend.
Original comment by fabrice....@gmail.com
on 12 Sep 2012 at 8:55
Done reporting. https://bugs.archlinux.org/task/31510
Original comment by martin.schumann
on 12 Sep 2012 at 9:06
Thanks for that.
Original comment by fabrice....@gmail.com
on 12 Sep 2012 at 12:39
Original issue reported on code.google.com by
martin.schumann
on 11 Sep 2012 at 2:54Attachments: