[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Pan-users] SIGSEGV @ socket-impl-gio.cc:502 (abort_flag)
From: |
Heinrich Mueller |
Subject: |
[Pan-users] SIGSEGV @ socket-impl-gio.cc:502 (abort_flag) |
Date: |
Mon, 24 Aug 2009 23:49:01 +0200 |
User-agent: |
Thunderbird 2.0.0.23 (X11/20090817) |
sorry for "crossposting", just don't know if "pan-devel" is still active :D
error:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f61faa28790 (LWP 12446)]
0x000000000052431a in pan::GIOChannelSocket::gio_func (this=0x3281b60,
channel=0x8e98340, cond=G_IO_IN) at socket-impl-gio.cc:502
502 if (_abort_flag) _listener->on_socket_abort (this);
OS: 64 bit ubuntu jaunty 9.04, latest version from SVN.
code snippet //
/if (_abort_flag)
{
_listener->on_socket_abort (this);
}
else if (!(cond & (G_IO_IN | G_IO_OUT)))
{
_listener->on_socket_error (this);
}
else // G_IO_IN or G_IO_OUT
{
const DoResult result = (cond & G_IO_IN) ? do_read () : do_write ();
/* if (_abort_flag) _listener->on_socket_abort (this);
else*/ if (result == IO_ERR) _listener->on_socket_error (this);
else if (result == IO_READ) set_watch_mode (READ_NOW);
else if (result == IO_WRITE) set_watch_mode (WRITE_NOW);
}/
//
sorry for not posting a backtrace, but the error just took too long to
be bothered
to be reproduced ...
isn't the second appearance of abort_flag a dupe? it was already checked
before by the first "if" branch...
i commented that and got no errors so far (opposed to random segfaults
before) :D
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Pan-users] SIGSEGV @ socket-impl-gio.cc:502 (abort_flag),
Heinrich Mueller <=