Hi. On Fri, 22 Aug 2014 11:06:54 -0400 laurent debian <laurent.deb...@gmail.com> wrote:
> I have this in my syslog and I am wondering what it is > pool[1655]: segfault at 72200 ip 00007fa419598200 sp 00007fa4149d30c0 > error 4 in libc-2.19.so[7fa419550000+19f000] Some binary received SIGSEGV signal. There're many reasons behind this, most of them usually boil down to the quality of source code and correctness of it. Usual way of dealing with these is to install debug symbols for the appropriate package and gdb, produce a core dump from the crash, use gdb to make a backtrace from the package and fill a bug report against a package. > and > kernel: [ 507.759144] perf samples too long (2509 > 2500), lowering > kernel.perf_event_max_sample_rate to 50000 > kernel:[ 3696.866261] perf samples too long (5006 > 5000), lowering > kernel.perf_event_max_sample_rate to 25000 It's harmless - see [1] comment 7. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1013708 Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140822202015.aa0b6fb654e3ffb43e61f...@gmail.com
