@Thayne,
No worries, and thanks for getting back to (not just) me. In fact, this
is not the first Java application with such Snoopy behaviour that I've
heard about.
https://github.com/a2o/snoopy/issues/215 will make sure thread safety
gets enabled by default starting with Snoopy version 2.5.0.
@Bostjan
I'm really sorry it took so long to get back to you. I just kept putting
it off because I was busy, and never got around to testing it.
But we recently ran into this issue again, and tested with building with
the --enable-thread-safety configure flag, and that did in fact fix the
issue.
@Thanye, I've checked the stack trace above again, and then inspected the git
history since 2.4.6 has been released in 2016, and only the following commits
have touched the src/datasource/cmdline.c file:
- 4b4ab04 Sun Oct 4 2020 +0200 GH #157: Fix (potentially*) incorrect malloc
size in
I can look at seeing if it can be reproduced with a newer version. 2.4.6
would be easier to test than 2.4.9, since it is in the apt repos for
18.04 and 20.04, but I might be able to compile 2.4.9 as well.
As far as reproducing it, I don't have great reproduction steps. I've
only seen this happen
@Thayne, can this one be reproduced with the latest Snoopy versions
(2.4.9)? If so, can you provide either a patch that fixes it, or a
method that I can use to reproduce the issue locally?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm not sure if this is the same issue. But while running BitBucket we
got a segfault about once a day (and had to restart bitbucket), until we
figured out it was coming from snoopy code and disabled snoopy on the
host.
The relevant part of the backtrace:
#1236 0x7fa0e54ac746 in strlen () at
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: snoopy (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698090
Title:
We found the bug. The problem was the syslog-ng configuration file.
/etc/syslog-ng/syslog-ng.conf
14.04:
unix-stream("/dev/log");
16.04:
unix-dgram("/dev/log");
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1698090
Title:
Segmentation fault
To manage notifications about this bug go to:
