[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#389353: marked as done (Problem with the libmal library which causes crash)



Your message dated Tue, 28 Nov 2006 22:13:22 +0100
with message-id <200611282213.22987.debian@pusling.com>
and subject line Problem with the libmal library which causes crash
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: libmal1
Version: 0.42-2_i386
Package file: libmal1_0.42-2_i386.deb
 
When the synchronise gets to executing mal, it crashes.  The backtrace is at 
the end of this email.

The problem was solved by reverting to libmal1_0.40-3_i386.deb

I am running Debian GNU/Linux sid using the following:

kernel 2.6.17-19
kde 3.5.4
kpilot 4.6.0 
pilot-link 0.11.8
Qt 3.3.6


Backtrace is:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1234958656 (LWP 32440)]
[KCrash handler]
#5  0xb7bf7385 in dlp_ReadRecordByIndex () from /usr/lib/libpisock.so.8
#6  0xb572ee03 in syncInfoNew () from /usr/lib/libmal.so.1
#7  0xb572efff in syncInfoNew () from /usr/lib/libmal.so.1
#8  0xb572f18c in syncInfoNew () from /usr/lib/libmal.so.1
#9  0xb57303c4 in malsync () from /usr/lib/libmal.so.1
#10 0xb5773044 in MALConduit::exec () from /usr/lib/kde3/conduit_mal.so
#11 0xb7bcd7c5 in SyncAction::execConduit () from /usr/lib/libkpilot.so.0
#12 0xb7bcd918 in SyncAction::qt_invoke () from /usr/lib/libkpilot.so.0
#13 0xb7bcd96b in ConduitAction::qt_invoke () from /usr/lib/libkpilot.so.0
#14 0xb576797b in MALConduit::qt_invoke () from /usr/lib/kde3/conduit_mal.so
#15 0xb6f5fb87 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0xb72e8c0b in QSignal::signal () from /usr/lib/libqt-mt.so.3
#17 0xb6f7f70a in QSignal::activate () from /usr/lib/libqt-mt.so.3
#18 0xb6f870dc in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#19 0xb6ef7aea in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#20 0xb6ef9907 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#21 0xb760552e in KApplication::notify () from /usr/lib/libkdecore.so.4
#22 0xb6e8b3d1 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#23 0xb6eea4e7 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#24 0xb6e9f71f in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#25 0xb6f1203d in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#26 0xb6f11e5e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#27 0xb6ef9683 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#28 0x080691ab in ?? ()
#29 0xbfa9c3d8 in ?? ()
#30 0x08079e08 in _IO_stdin_used ()
#31 0x00000001 in ?? ()
#32 0x00000000 in ?? ()



Regards

Peter Robin

Attachment: pgpj0DxVLg5IH.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
Version: 4:3.5.5.dfsg.1-2

The malconduit is gone and is not coming back unless there shows up new people 
in the kpilot upstream development showing interesting in malconduit.
Closing this bug.

/Sune
-- 
Do you know how to reinstall a laser device from Netscape?

You neither can ever log in the operating system on a monitor, nor ever have 
to configure the connection and therefore you must save from a analogic BIOS 
provider of the port for cancelling the tool.

Attachment: pgp8PEkrgR7mg.pgp
Description: PGP signature


--- End Message ---

Reply to: