Thomas Reitelbach wrote:


A "strace" output is not very useful for us.
Please don't use strace, but instead compile licq (both, daemon _and_ qt-gui) with the --enable-debug switch.
Then run licq and send us the backtrace that is generated when it crashes.


Did your run the upgrade-1.3.0.sh script? CVS version requires this script when you want to re-use your old licq configuration.

Thomas




Ok.. sorry about this. it turned out to be the configfile after all, even though I am sure I ran
the cvs version before reinstallation it probably was a bit too old since I updated
it. But that aside it still crashed the same way and did not take enable-debug, which
I found strange.. Oh well, it works, and I shall now go stick my head in the snow here
as punishment for not checking the config file formats.. Thanx anyways for the pointers.


On a side note.. would it not be an idea to set a config file version number, for each "incompatible"
update?? that way licq would not just crash, but could give an intelligent error and shut down.


/Roger




------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel

Reply via email to