Running 'continue' doesn't help, if you could run 'bt full' that would
provide much more useful information about where the crash occurs.
Unfortunately, this bug report doesn't contain any information at all
about the crash. Can you re-send a proper one?
Jon
-
I connected to my msn account with another client while the
licq-msn-plugin was running and connected.
Hope this is more useful than my last ones:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1259734096 (LWP 6248)]
0x08097805 in INetSocket::SendRaw (this=0x0, b=0x8293
Hello,
this happens about every 30 minutes(when I'm chatting):
16:49:01: [SRV] Message from someone (**).
playing /usr/share/sounds/KDE_Beep_Beep.wav
[Thread -1259799632 (zombie) exited]
Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread -1259799632 (zombie)]
0x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 14 March 2004 07:19 am, wrote:
> Happened when i opened the plugin manager. Sadly there was not made a
> corefile... You need it?
> The bug is reproduceable, but sadly my memory isn't... what again was
> the command to tell something to crea
Thomas Reitelbach wrote:
On Saturday 13 March 2004 23:19, wrote:
Happened when i opened the plugin manager. Sadly there was not made a
corefile... You need it?
The bug is reproduceable, but sadly my memory isn't... what again was
the command to tell something to create a corefile
The backtrace. Looks like a QT-bug.
FC 1
qt-3.1.2-14
gcc-3.3.2-1
Core was generated by `licq -d 31'.
Program terminated with signal 6, Aborted.
Reading symbols from /lib/libssl.so.4...done.
Loaded symbols for /lib/libssl.so.4
Reading symbols from /lib/libcrypto.so.4...done.
Loaded symbols for /lib
On Saturday 13 March 2004 23:19, wrote:
> Happened when i opened the plugin manager. Sadly there was not made a
> corefile... You need it?
> The bug is reproduceable, but sadly my memory isn't... what again was
> the command to tell something to create a corefile anyway?
"ulimit -c unlimited"
Th
Happened when i opened the plugin manager. Sadly there was not made a
corefile... You need it?
The bug is reproduceable, but sadly my memory isn't... what again was
the command to tell something to create a corefile anyway?
/Arjen
Licq Segmentation Violation Detected.
Backtrace:
licq(licq_handl
On Tuesday 19 August 2003 09:57, Christian B. Wiik wrote:
> Current CVS.
>
> Another thing. When I drag a contact into the messagebox when in message
> mode, I get "Licq" in the window. Supposed to be like this?
> Shouldn't it switch to sending contacts mode?
See http://marc.theaimsgroup.com/
Easy reproducable:
Open a chatmode messageview.
- Select contact list in drop down.
- Select Message again -> crash.
Current CVS.
Another thing. When I drag a contact into the messagebox when in message
mode, I get "Licq" in the window. Supposed to be like this?
Shouldn't it switch to sending
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 06 July 2003 08:18 pm, Juan F. Codagnone wrote:
> On Friday 04 July 2003 07:11, Christian B. Wiik wrote:
> > Easy reproducable: Utilities -> hostname -> Run -> Close window ->
> > crash.
>
> my fix.
Thanks, applied.
Jon
___
On Friday 04 July 2003 07:11, Christian B. Wiik wrote:
> Easy reproducable: Utilities -> hostname -> Run -> Close window ->
> crash.
my fix.
--
Buenos Aires, Argentina 13°C with winds at 5 km/h WNW
Index: plugins/qt-gui//src/mainwin.cpp
==
On Friday 04 July 2003 07:11, Christian B. Wiik wrote:
> Easy reproducable: Utilities -> hostname -> Run -> Close window ->
> crash.
hi. backtrace in binaries without debuging symbols are not very usefulls.
[New Thread 16384 (LWP 2649)]
[New Thread 32769 (LWP 2650)]
[New Thread 16386 (LWP 2651)]
Easy reproducable: Utilities -> hostname -> Run -> Close window ->
crash.
Licq Segmentation Violation Detected.
Backtrace:
licq(licq_handle_sigsegv+0x7f) [0x80bdfa7]
/lib/i686/libpthread.so.0 [0x4013674e]
/lib/i686/libc.so.6 [0x42028558]
/usr/local/lib/licq/licq_qt-gui.so(_ZN11CUtilityDlgD0Ev+0xbd
Hi,
licq crashes reproducibly when dragging one user over another (as for
sending the contact) if there is already an open message window for
the other user.
i.e. double click on user a, drag user b over user a, voila.
licq from current cvs, qt 3.0.5-3 (debian sarge)
Or is this a QT problem?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
my licq crashed while i was typing a message. yeah. it will be hard to fix
this.
the last things that are in my licq's logfile is:
QGArray::at: Absolute index 456 out of range
QGArray::at: Absolute index 456 out of range
QGArray::at: Absolute index
[Jon Keating <[EMAIL PROTECTED]>]
> On Thursday 14 November 2002 03:26 am, Christian B. Wiik wrote:
>> Happened when I pressed "Send".
>
> And this happens with both current daemon and qt-gui?
Yes, up to date as of today. Only happened once though.
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 14 November 2002 03:26 am, Christian B. Wiik wrote:
> Happened when I pressed "Send".
And this happens with both current daemon and qt-gui?
Jon
__
Jon Keating
Happened when I pressed "Send".
latest greatest CVS, running RedHat 8.0 qt-3.0.5
Licq Segmentation Violation Detected.
Backtrace:
licq(licq_handle_sigsegv+0x7f) [0x80b2103]
licq [0x42028c48]
/usr/lib/qt3-gcc3.2/lib/libqt-mt.so.3(_ZN12QTextCommandD2Ev+0x4e) [0x40604e3e]
/usr/lib/qt3-gcc3.2/lib/li
hi today when i launch licq and it load contact from server it crashed and
produce core dump,
in debug it give me tihis backtrace , what's the problem?
(gdb) bt full
#0 0x401de621 in kill () from /lib/libc.so.6
No symbol table info available.
#1 0x4012226b in raise (sig=6) at signals.c:65
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
crash data:
20:13:31: [SRV] Logging off.
20:13:31: [PKT] Packet (SRVv0, 6 bytes) sent:
~(213.93.75.69:32912 -> 205.188.10.117:5190)
~ : 2A 04 27 56 00 00 *.'V..
20:13:31: [ERR] Internal error:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This crash allways occurs when sending a message through serverm when
sending directly times out (or failes).
Hope its usefull, Arjen Heidinga
Oh, of course latest CVS :)
- Licqs dump
00:32:53: [WRN] Connect to Ðîzz¥ (12619538) failed:
~
Hi, got this crash when a user sent me a message:
23:25:13: [TCP] Connection from Mongi (***) [v6].
23:25:13: [TCP] Message from Mongi (***).
Licq Segmentation Violation Detected.
Backtrace:
licq(licq_handle_sigsegv+0x73) [0x80a5c7b]
/lib/libpthread.so.0 [0x4010ef54]
/lib/libc.so.6 [0x401
Hi to all, my Licq is crashed when i drop a contact, and generate a core, i
was compiled with debugging info and i can use
gdb pathsrc/licq pathcore/core
i done to prompt of gdb
bt full and i give
(gdb) bt full
#0 0x401de621 in kill () from /lib/libc.so.6
No symbol table info available.
#
Hi,
Searching for a new user by UIN with the qt plugin gives this error when
the search button is hit. licq then crashes after a while.
./local/licq/bin/licq: relocation error:
/home/vanion/local/licq-020214/lib/licq/licq_qt-gui.so: undefined
symbol: icqSearchByUin__10CICQDaemonUl
I am using th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi !
My licq-daily builds crashes since licq-20011215. This is the one, which runs
perfectly (authorisation and some other things dont work perfect), but later
builds allways crash during starting (SIGSEGV)
I use following parameters to compile and
On January 21, 2002 4:03 am, Kevin wrote:
> I downloaded the daily today, compiled everything with no errors. When I
> try to run, the GUI seems to crash, yet Licq still seems to connect.
I think this is a known bug. Try running licq as follows:
licq -- --style default -spli
(or whatever licq
I downloaded the daily today, compiled everything with no errors. When I try
to run, the GUI seems to crash, yet Licq still seems to connect.
System:
Slackware 8.0
gcc 2.95.3
QT 2.3.1
KDE 2.2.2
Here's the -d 15 output:
bash-2.05$ licq -d 15
14:31:30: [WRN] Licq: Ignoring stale lockfile (pid
It's not a bug, and you don't have to change anything in your setup.
The feature simply hasn't been implemented yet. Next time, it would be
wise to search the list archives at least briefly before letting us know
"something is wrong"...it has been said many times that this
functionality is not t
29 matches
Mail list logo
