Re: licq 1.5.1 Segmentation Violation Detected

Hello,

It is installed from FreeBSD ports with default options ( for all
packages it depends, and default options for dependencies packages ).
FreeBSD is 8.2-STABLE Thu Jul 28 11:04:34 with ports from 11.08.2011
15:17.
It used to work before I switched to 1.5.1.

I was with working Licq 1.5.0 but I saw there is a new version, and
upgraded all packages on the OS ( with recursive recompile of all of
it because of depends ).

Now, it happens every time when I start it ( I attached debug info 1st
level to see that I successfully login to server, then I choose to go
online, a couple of seconds and it crashes).

Until now I didn't try to enable IPv6 in kernel, because Licq says it
is only warning, but it is not problem for me to build IPv6 on the OS.

Sorry I didn't attached build process, I'm with debug flags of cmake
port (because in Licq 1.5.0 there was some error with assertation
failed, but it is not Licq 1.5.0 bug - it happens when FreeBSD
packages are not fully synced ).

http://bobi.gateit.net:7880/_licq/licq-1.5.1.make.txt build process
from the port
http://bobi.gateit.net:7880/_licq/licq-1.5.1.make_install.txt install
process from the port
http://bobi.gateit.net:7880/_licq/cmake.warning.on.licq-qt4.txt -
cmake warning on build process on licq-qt plugin from the ports

In 2 days I'll attach build and install process from the QT4 plugin,
and debug info on building from source and licq.backtrace.gdb (sorry
now I lost connection to my PC, may be power failure).

Thank you




On Aug 12, 6:12=A0pm, Anders Olofsson <[email protected]> wrote:
> On 2011-08-12 12:44, quintessence wrote:
>
>
>
> > FreeBSD 8.2 amd64 (without IPv6)
>
> > 13:35:46.860 [INF] licq: [SRV] Received end of contact list.
> > 13:35:46.884 [INF] licq: [SRV] Activating server contact list.
> > 13:35:46.985 [INF] licq: Meta request failed. Eventid 22, errorcode 35
> > Licq Segmentation Violation Detected.
>
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 80180a900 (LWP 100406/licq)]
> > 0x00000000004f2a86 in IcqProtocol::ProcessDoneEvent ()
>
> > #0 =A00x00000008014fbf9c in thr_kill () from /lib/libc.so.7
> > #1 =A00x0000000801598718 in abort () from /lib/libc.so.7
> > #2 =A00x0000000000488258 in licq_install_signal_handlers ()
> > #3<signal handler called>
> > #4 =A00x00000000004f2a86 in IcqProtocol::ProcessDoneEvent ()
> > #5 =A00x00000000004fc9e7 in IcqProtocol::ProcessVariousFam ()
> > #6 =A00x00000000005170e3 in IcqProtocol::ProcessDataChannel ()
> > #7 =A00x0000000000517227 in IcqProtocol::ProcessSrvPacket ()
> > #8 =A00x0000000000570a7f in MonitorSockets_tep ()
> > #9 =A00x00000008013964d1 in pthread_getprio () from /lib/libthr.so.3
> > #10 0x0000000000000000 in ?? ()
> > Cannot access memory at address 0x7fffff7fd000
>
> Hi and thanks for reporting the crash.
>
> This is not something I've seen before and I'm going to need more
> information to solve it...
>
> Does this happen every time, sometimes or just once?
>
> Has it worked before with Licq 1.5.1 or with an older version of Licq?
> (in the later case, which version(s))
>
> Did you build Licq yourself or did you get it pre-compiled?
>
> If it's reproducible, could you please build with debugging enabled and
> attach licq.backtrace.gdb. (Enable debugging by adding
> -DCMAKE_BUILD_TYPE=3DDebug to cmake command before building)
>
> /Anders