aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Crash while doing nothing in particular  (Read 1516 times)

phoenix

  • Evil respawning bird from aMule Dev Team
  • Developer
  • Hero Member
  • *****
  • Karma: 44
  • Offline Offline
  • Posts: 2503
  • The last shadow you'll ever see
Crash while doing nothing in particular
« on: January 03, 2007, 01:52:19 PM »

I was just web browsing and compiling aMule in the background :evil: and got this crash:
Code: [Select]
--------------------------------------------------------------------------------
A fatal error has occurred and aMule has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
    [URL]http://forum.amule.org/board.php?boardid=67[/URL]
If possible, please try to generate a real backtrace of this crash:
    [URL]http://www.amule.org/wiki/index.php/Backtraces[/URL]

----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMule CVS using wxGTK2 v2.8.0 (Debugging) (Snapshot: rev. 7024)
Running on: Linux 2.6.17-1.2142_FC4 i686

[2] CamuleApp::OnFatalException() in amule.cpp:1251
[3] wxFatalSignalHandler in /usr/local/wxWidgets-cvsu/lib/libwx_baseud-2.8.so.0[0xa096ab]
[4] ?? in [0x34b420]


--------------------------------------------------------------------------------
Aborted (core dumped)
$ gdb trunk/src/amule core.6451
GNU gdb Red Hat Linux (6.3.0.0-1.84rh)
Copyright 2004 Free Software Foundation, Inc.
...
(gdb) bt
#0  0x0034b402 in __kernel_vsyscall ()
#1  0x00391f90 in raise () from /lib/libc.so.6
#2  0x00393678 in abort () from /lib/libc.so.6
#3  0x00a096b3 in wxFatalSignalHandler () at ./src/unix/utilsunx.cpp:1106
#4  
#5  0x00000000 in ?? ()
#6  0x0064cc51 in _GSocket_GDK_Input (data=0xd278bd8, source=306, condition=GDK_INPUT_WRITE) at ./src/gtk/gsockgtk.cpp:36
#7  0x00294800 in gdk_get_show_events () from /usr/lib/libgdk-x11-2.0.so.0
#8  0x00c3b4fc in g_vasprintf () from /usr/lib/libglib-2.0.so.0
#9  0x00c154ce in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#10 0x00c184d6 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#11 0x00c187c3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#12 0x05562a46 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#13 0x0064a9b0 in wxEventLoop::Run (this=0xb4b5f78) at ./src/gtk/evtloop.cpp:76
#14 0x006e3d29 in wxAppBase::MainLoop (this=0x903af90) at ./src/common/appcmn.cpp:308
#15 0x006e3eb3 in wxAppBase::OnRun (this=0x903af90) at ./src/common/appcmn.cpp:363
#16 0x0098b265 in wxEntry (argc=@0xa99d8c, argv=0x902a090) at ./src/common/init.cpp:449
#17 0x0098b340 in wxEntry (argc=@0xbfddeaf0, argv=0xbfddeb74) at ./src/common/init.cpp:461
#18 0x0821d8f2 in main (argc=2, argv=0xbfddeb74) at amule-gui.cpp:95
(gdb) frame 6
#6  0x0064cc51 in _GSocket_GDK_Input (data=0xd278bd8, source=306, condition=GDK_INPUT_WRITE) at ./src/gtk/gsockgtk.cpp:36
36          socket->Detected_Write();
(gdb) l
31        GSocket *socket = (GSocket *)data;
32
33        if (condition & GDK_INPUT_READ)
34          socket->Detected_Read();
35        if (condition & GDK_INPUT_WRITE)
36          socket->Detected_Write();
37      }
38      }
39
40      bool GSocketGUIFunctionsTableConcrete::CanUseEventLoop()
(gdb) p socket
$1 = (class GSocket *) 0xd278bd8
(gdb) p condition
$2 = GDK_INPUT_WRITE
(gdb) p *socket
warning: can't find linker symbol for virtual table for `GSocket' value
$3 = {_vptr.GSocket = 0x490d34, m_ok = 20, m_fd = -1968, m_local = 0x34, m_peer = 0xf176814, m_error = 80, m_non_blocking = 52, m_server = false,
  m_stream = true, m_establishing = false, m_reusable = 20, m_timeout = 598104, m_detected = 53, m_cbacks = {0x14, 0x50, 0x34, 0x14}, m_data = {
    0x50
, 0x34
, 0x14
, 0x2d8
},
  m_gui_dependent = 0x50
}
(gdb)
You see the importance of using a debug enabled version? And the importance of using gdb? The aMule backtrace says nothing, by the simple reason that the problem is not in aMule. I never get this error with wx-2.6.3, and *always* get this error with wx-2.8.0. So, if there is any wx dev around, please, ...
Logged