Hi,
we are unfortunately still seeing segfaults with pgadmin3 on Debian:
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
07:49:15: Debug: Adding duplicate image handler for 'PNG file'
[New Thread 0x7fffe606a700 (LWP 4318)]
Program received signal SIGSEGV, Segmentation fault.
__lll_unlock_elision (lock=0x132c5e0, private=0)
at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
29 ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c: Datei oder Verzeichnis
nicht gefunden.
(gdb) bt
#0 __lll_unlock_elision (lock=0x132c5e0, private=0)
at ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
#1 0x00007ffff5906290 in ?? ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#2 0x0000000000794b60 in ?? ()
#3 0x00007ffff579ed5e in wxAppConsoleBase::CallEventHandler(wxEvtHandler*,
wxEventFunctor&, wxEvent&) const ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#4 0x00007ffff593bad8 in
wxEvtHandler::ProcessEventIfMatchesId(wxEventTableEntryBase const&,
wxEvtHandler*, wxEvent&) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#5 0x00007ffff593bbdb in wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*)
() from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#6 0x00007ffff593bf88 in wxEvtHandler::TryHereOnly(wxEvent&) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#7 0x00007ffff593bd93 in wxEvtHandler::DoTryChain(wxEvent&) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#8 0x00007ffff593c075 in wxEvtHandler::ProcessEvent(wxEvent&) ()
from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
#9 0x00007ffff652e088 in wxWindowBase::TryAfter(wxEvent&) ()
from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
#10 0x00007ffff65a102b in wxScrollHelperEvtHandler::ProcessEvent(wxEvent&) ()
from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-3.0.so.0
I'm not sure if this is a pgadmin3 bug, or something in wx itself.
The above backtrace is from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797804
though it looks the same as the old bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750557
and the 4 other reports merged into the last one.
It works on my machine so I can't reproduce it, but there were reports
from different sources.
Does anyone have an idea?
Christoph
--
cb@df7cb.de | http://www.df7cb.de/