Re[2]: segfault with latest wx
Nerijus Baliunas <[email protected]>
| Newsgroups | gmane.mail.mahogany.devel |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 26 Jul 2004 19:06:52 +0200 (Romance Daylight Time) Vadim Zeitlin <[email protected]> wrote: VZ> NB> #0 0x402b9577 in _GSocket_GDK_Input (data=0x84232e0, source=9, VZ> NB> condition=GDK_INPUT_WRITE) at ../wxWindows/src/gtk/gsockgtk.c:33 VZ> NB> #1 0x40a5319b in gdk_get_show_events () from /usr/lib/libgdk-1.2.so.0 VZ> NB> #2 0x084232e0 in ?? () VZ> NB> #3 0x00000009 in ?? () VZ> NB> #4 0x00000002 in ?? () VZ> NB> #5 0x40a95710 in ?? () from /usr/lib/libglib-1.2.so.0 VZ> VZ> The backtrace is compeltely useless and I don't understand at all how does VZ> it get into _GSocket_GDK_Input as M doesn't use wxSocket at all :-( Any VZ> hints about how to reproduce it? I know it's useless, *but* yesterday you applied some patch dealing with it, and today I read in wx-dev somebody was complaining about _GSocket_* on wxmsw. That's why I posted it here. Don't you get segfault at startup on Linux? Regards, Nerijus ------------------------------------------------------- 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