Re: Re: licq 1.5.1 Segmentation Violation Detected

On 2011-08-12 22:38, quintessence wrote:
> 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 ).

Ok, this is good. There wasn't too much changes between 1.5.0 and 1.5.1 
so it should limit the possible causes significantly.

> 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.

IPv6 is not required in any way for Licq to work and it isn't used for 
ICQ protocol anyway so you will be fine without it.

> 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

Hopefully I figured out the cmake warning and it should now be fixed for 
future releases.

> 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).

Alright, I'll be waiting for the backtrace, it should make the 
troubleshooting much easier.

/Anders