From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-September/018569.html | 99 +++++++++++++++++++++++++++ 1 file changed, 99 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-September/018569.html (limited to 'zarb-ml/mageia-dev/2012-September/018569.html') diff --git a/zarb-ml/mageia-dev/2012-September/018569.html b/zarb-ml/mageia-dev/2012-September/018569.html new file mode 100644 index 000000000..539328011 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-September/018569.html @@ -0,0 +1,99 @@ + + + + [Mageia-dev] pthread segfaults? + + + + + + + + + +

[Mageia-dev] pthread segfaults?

+ Antoine Pitrou + solipsis at pitrou.net +
+ Sat Sep 8 19:01:48 CEST 2012 +

+
+ +
On Sat, 08 Sep 2012 13:00:32 +0200
+eatdirt <dirteat at gmail.com> wrote:
+> Hi,
+> am I alone to get pthread segfaults in the log for various programs??
+> 
+> upowerd[759]: segfault at 0 ip 00007f7a03efbfe0 sp 00007fff5497d498 
+> error 4 in libc-2.16.so[7f7a03dfc000+1a2000]
+> 
+> motion[3066]: segfault at 18 ip 00007f98abe78b80 sp 00007fffdbfa6678 
+> error 4 in libpthread-2.16.so[7f98abe6f000+16000]
+
+A segfault "in" libpthread doesn't mean libpthread is at fault. The
+application (or another library) may simply have handed it an invalid
+pointer.
+
+Regards
+
+Antoine.
+
+
+-- 
+Software development and contracting: http://pro.pitrou.net
+
+
+
+ + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1