aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Program received signal SIGSEGV, Segmentation fault  (Read 5031 times)

unknown

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 3
Program received signal SIGSEGV, Segmentation fault
« on: January 03, 2006, 10:49:17 PM »

SuSE 9.2
wxGTK-2.6.2
aMule-2.1.0

Code: [Select]
(gdb) bt
#0  0x408a17d3 in main_arena () from /lib/tls/libc.so.6
#1  0x402ce4c9 in _GSocket_GDK_Input ()
   from /usr/local/lib/libwx_gtk2_core-2.6.so.0
#2  0x40b8697b in gdk_io_invoke () from /opt/gnome/lib/libgdk-x11-2.0.so.0
#3  0x40cdfd5f in g_io_unix_dispatch () from /opt/gnome/lib/libglib-2.0.so.0
#4  0x40cb8d17 in g_main_context_dispatch ()
   from /opt/gnome/lib/libglib-2.0.so.0
#5  0x40cbb467 in g_main_context_iterate ()
   from /opt/gnome/lib/libglib-2.0.so.0
#6  0x40cbc677 in g_main_loop_run () from /opt/gnome/lib/libglib-2.0.so.0
#7  0x409b9e43 in gtk_main () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#8  0x402cc333 in wxEventLoop::Run ()
   from /usr/local/lib/libwx_gtk2_core-2.6.so.0
#9  0x403539f9 in wxAppBase::MainLoop ()
   from /usr/local/lib/libwx_gtk2_core-2.6.so.0
#10 0x403537c3 in wxAppBase::OnRun ()
   from /usr/local/lib/libwx_gtk2_core-2.6.so.0
#11 0x406049b0 in wxEntry () from /usr/local/lib/libwx_base-2.6.so.0
#12 0x08159f19 in main (argc=1, argv=0xbffff0e4) at amule-gui.cpp:145
(gdb) bt full
#0  0x408a17d3 in main_arena () from /lib/tls/libc.so.6
No symbol table info available.
#1  0x402ce4c9 in _GSocket_GDK_Input ()
   from /usr/local/lib/libwx_gtk2_core-2.6.so.0
No symbol table info available.
#2  0x40b8697b in gdk_io_invoke () from /opt/gnome/lib/libgdk-x11-2.0.so.0
No symbol table info available.
#3  0x40cdfd5f in g_io_unix_dispatch () from /opt/gnome/lib/libglib-2.0.so.0
No symbol table info available.
#4  0x40cb8d17 in g_main_context_dispatch ()
   from /opt/gnome/lib/libglib-2.0.so.0
No symbol table info available.
#5  0x40cbb467 in g_main_context_iterate ()
   from /opt/gnome/lib/libglib-2.0.so.0
No symbol table info available.
#6  0x40cbc677 in g_main_loop_run () from /opt/gnome/lib/libglib-2.0.so.0
No symbol table info available.
#7  0x409b9e43 in gtk_main () from /opt/gnome/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#8  0x402cc333 in wxEventLoop::Run ()
   from /usr/local/lib/libwx_gtk2_core-2.6.so.0
No symbol table info available.
#9  0x403539f9 in wxAppBase::MainLoop ()
---Type to continue, or q to quit---
   from /usr/local/lib/libwx_gtk2_core-2.6.so.0
No symbol table info available.
#10 0x403537c3 in wxAppBase::OnRun ()
   from /usr/local/lib/libwx_gtk2_core-2.6.so.0
No symbol table info available.
#11 0x406049b0 in wxEntry () from /usr/local/lib/libwx_base-2.6.so.0
No symbol table info available.
#12 0x08159f19 in main (argc=1, argv=0xbffff0e4) at amule-gui.cpp:145
No locals.
(gdb) thread apply all bt

Thread 4 (Thread 1105214384 (LWP 16629)):
#0  0xffffe410 in ?? ()
#1  0x41e038c8 in ?? ()
#2  0x000002ab in ?? ()
#3  0x00000000 in ?? ()
#4  0x400368ec in pthread_cond_timedwait@@GLIBC_2.3.2 ()
   from /lib/tls/libpthread.so.0
#5  0x40661e87 in wxConditionInternal::WaitTimeout ()
   from /usr/local/lib/libwx_base-2.6.so.0
#6  0x40661ee2 in wxCondition::WaitTimeout ()
   from /usr/local/lib/libwx_base-2.6.so.0
#7  0x40663259 in wxSemaphoreInternal::WaitTimeout ()
   from /usr/local/lib/libwx_base-2.6.so.0
#8  0x40663322 in wxSemaphore::WaitTimeout ()
   from /usr/local/lib/libwx_base-2.6.so.0
#9  0x0822775f in CTimerThread::Entry (this=0x8601998) at Timer.cpp:66
#10 0x4066374f in wxThreadInternal::PthreadStart ()
   from /usr/local/lib/libwx_base-2.6.so.0
#11 0x406637cc in wxPthreadStart () from /usr/local/lib/libwx_base-2.6.so.0
#12 0x400347f3 in start_thread () from /lib/tls/libpthread.so.0
#13 0x4084562a in clone () from /lib/tls/libc.so.6

---Type to continue, or q to quit---
Thread 2 (Thread 1103113136 (LWP 16627)):
#0  0xffffe410 in ?? ()
#1  0x41c02808 in ?? ()
#2  0x4069a690 in ?? () from /usr/local/lib/libwx_base-2.6.so.0
#3  0x00000000 in ?? ()
#4  0x40039786 in __nanosleep_nocancel () from /lib/tls/libpthread.so.0
#5  0x4066bf6a in wxMicroSleep () from /usr/local/lib/libwx_base-2.6.so.0
#6  0x4066bfa8 in wxMilliSleep () from /usr/local/lib/libwx_base-2.6.so.0
#7  0x40661c1c in wxThread::Sleep () from /usr/local/lib/libwx_base-2.6.so.0
#8  0x08125f08 in UploadBandwidthThrottler::Entry (this=0x88d79b8)
    at UploadBandwidthThrottler.cpp:354
#9  0x4066374f in wxThreadInternal::PthreadStart ()
   from /usr/local/lib/libwx_base-2.6.so.0
#10 0x406637cc in wxPthreadStart () from /usr/local/lib/libwx_base-2.6.so.0
#11 0x400347f3 in start_thread () from /lib/tls/libpthread.so.0
#12 0x4084562a in clone () from /lib/tls/libc.so.6

Thread 1 (Thread 1089849632 (LWP 16618)):
#0  0x408a17d3 in main_arena () from /lib/tls/libc.so.6
#1  0x402ce4c9 in _GSocket_GDK_Input ()
   from /usr/local/lib/libwx_gtk2_core-2.6.so.0
#2  0x40b8697b in gdk_io_invoke () from /opt/gnome/lib/libgdk-x11-2.0.so.0
#3  0x40cdfd5f in g_io_unix_dispatch () from /opt/gnome/lib/libglib-2.0.so.0
---Type to continue, or q to quit---
#4  0x40cb8d17 in g_main_context_dispatch ()
   from /opt/gnome/lib/libglib-2.0.so.0
#5  0x40cbb467 in g_main_context_iterate ()
   from /opt/gnome/lib/libglib-2.0.so.0
#6  0x40cbc677 in g_main_loop_run () from /opt/gnome/lib/libglib-2.0.so.0
#7  0x409b9e43 in gtk_main () from /opt/gnome/lib/libgtk-x11-2.0.so.0
#8  0x402cc333 in wxEventLoop::Run ()
   from /usr/local/lib/libwx_gtk2_core-2.6.so.0
#9  0x403539f9 in wxAppBase::MainLoop ()
   from /usr/local/lib/libwx_gtk2_core-2.6.so.0
#10 0x403537c3 in wxAppBase::OnRun ()
   from /usr/local/lib/libwx_gtk2_core-2.6.so.0
#11 0x406049b0 in wxEntry () from /usr/local/lib/libwx_base-2.6.so.0
#12 0x08159f19 in main (argc=1, argv=0xbffff0e4) at amule-gui.cpp:145

Hope it's helpfull!
Logged

Kry

  • Ex-developer
  • Retired admin
  • Hero Member
  • *****
  • Karma: -665
  • Offline Offline
  • Posts: 5795
Re: Program received signal SIGSEGV, Segmentation fault
« Reply #1 on: January 03, 2006, 11:42:11 PM »

wxWidgets fault. It's fixed on the CVS version of wx, and you might be able to find a patch somewhere on the forum.
Logged

Gerd78

  • Hero Member
  • *****
  • Karma: 9
  • Offline Offline
  • Posts: 681
Re: Program received signal SIGSEGV, Segmentation fault
« Reply #2 on: January 03, 2006, 11:52:41 PM »

Did you build wxWidgets from source?

If not: Contact the person who made it and ask him/her to add this patch to the package.

If so: Apply the patch yourself and then rebuild wxWidgets 2.6.2 or use this CVS tarball and then rebuild aMule against that.

If you don't want to do that, you can

- "rm -f ${prefix}/share/locale/*/LC_MESSAGES/amule.mo" and then rebuild aMule with "./configure --disable-nls" where "${prefix}" is the prefix of your current aMule installation, or
- make sure that aMule starts in English locale by setting "export LC_ALL=C" and executing aMule from the same shell, unless you already changed the locale in the preferences - then you will have to edit the "Language=" line in "~/.aMule/amule.conf" manually.
Logged

ken

  • Hero Member
  • *****
  • Karma: 4
  • Offline Offline
  • Posts: 825
Re: Program received signal SIGSEGV, Segmentation fault
« Reply #3 on: January 04, 2006, 03:34:39 AM »

Actually, Gerd78, I think this user is encountering the wx sockets bug, not the locale bug.  So, the patch and locale workaround that you suggest is not for the crash he/she is experiencing.

On the other hand, the pointer to the CVS HEAD source tarball would fix it either way. ;)
Logged

unknown

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 3
Re: Program received signal SIGSEGV, Segmentation fault
« Reply #4 on: January 04, 2006, 01:56:43 PM »

Thanks it's working. I've compiled the CVS tarball and aMule did not crash again, yet.

Greetings
unknown
Logged

Arichy

  • Full Member
  • ***
  • Karma: 0
  • Offline Offline
  • Posts: 224
Re: Program received signal SIGSEGV, Segmentation fault
« Reply #5 on: January 07, 2006, 12:00:46 PM »

Quote
Originally posted by Gerd78
make sure that aMule starts in English locale by setting "export LC_ALL=C" and executing aMule from the same shell, unless you already changed the locale in the preferences - then you will have to edit the "Language=" line in "~/.aMule/amule.conf" manually.

Why have to edit amule.conf manually? define "language=C" there ? Can't language be set to "English (USA)" within aMule?
Logged
Gentoo i686

Gerd78

  • Hero Member
  • *****
  • Karma: 9
  • Offline Offline
  • Posts: 681
Re: Program received signal SIGSEGV, Segmentation fault
« Reply #6 on: January 07, 2006, 12:38:45 PM »

Quote
Originally posted by Arichy
Why have to edit amule.conf manually?
I don't understand your question. What's your problem?
Quote
Originally posted by Arichy
define "language=C" there ?
No, delete that line.
Quote
Originally posted by Arichy
Can't language be set to "English (USA)" within aMule?
Not if it crashes on startup. Does it crash on startup for you? If not, simply ignore this thread completely.
Logged

ecforum

  • Full Member
  • ***
  • Karma: 1
  • Offline Offline
  • Posts: 105
Re: Program received signal SIGSEGV, Segmentation fault
« Reply #7 on: January 07, 2006, 06:24:30 PM »

I had the same pb.
It seems ok using the CVS tarball of wxWidgets-2.6.2.

Thanks
Logged