Re: segfault with latest wx
Vadim Zeitlin <[email protected]>
| Newsgroups | gmane.mail.mahogany.devel |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 26 Jul 2004 17:41:06 +0300 (EEST) Nerijus Baliunas <[email protected]> wrote: NB> Program received signal SIGSEGV, Segmentation fault. When does it happen? NB> [Switching to Thread 16384 (LWP 23091)] NB> 0x402b9577 in _GSocket_GDK_Input (data=0x84232e0, source=9, NB> condition=GDK_INPUT_WRITE) at ../wxWindows/src/gtk/gsockgtk.c:33 NB> 33 socket->m_functions->Detected_Write(socket); NB> Current language: auto; currently c NB> (gdb) bt NB> #0 0x402b9577 in _GSocket_GDK_Input (data=0x84232e0, source=9, NB> condition=GDK_INPUT_WRITE) at ../wxWindows/src/gtk/gsockgtk.c:33 NB> #1 0x40a5319b in gdk_get_show_events () from /usr/lib/libgdk-1.2.so.0 NB> #2 0x084232e0 in ?? () NB> #3 0x00000009 in ?? () NB> #4 0x00000002 in ?? () NB> #5 0x40a95710 in ?? () from /usr/lib/libglib-1.2.so.0 The backtrace is compeltely useless and I don't understand at all how does it get into _GSocket_GDK_Input as M doesn't use wxSocket at all :-( Any hints about how to reproduce it? Thanks, VZ ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click