@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 cmdline
- ede16a4 Mon Nov 25 2019 + correct pointer vs byte compare in cmdline.c
- e989f26 Thu Jul 27 2017 +0200 Make snoopy compile on 64-bit Arch Linux with
GCC 7.1.1
None of these commits seems to be resolving an issue that could
potentially result in a segmentation fault.
However, "cmdline" datasource is one of the two Snoopy datasources that are
accessing Snoopy's "global" (in the context of a single process) data storage
facility. If your application is heavily threaded, this could potentially
result in a segmentation fault, if the conditions are just right.
Therefore, only upgrading to 2.4.9 should not resolve this particular issue as
far as I can see now. But using the --enable-thread-safety ./configure flag
might.
If you're willing to build Snoopy yourself with the --enable-thread-safety flag
and test this hypothesis out, let me know the outcome. I am looking at
switching thread safety build flag from default off to default on in the
upcoming 2.5.0 release.
--
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:
https://bugs.launchpad.net/ubuntu/+source/snoopy/+bug/1698090/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
