Bug 132613 - crash incoming files greater than one kilobyte
Summary: crash incoming files greater than one kilobyte
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kde-bluetooth
Classification: Unmaintained
Component: kbtobexsrv (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-19 00:06 UTC by Marcos Saiz
Modified: 2018-09-04 18:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcos Saiz 2006-08-19 00:06:16 UTC
Version:            (using KDE KDE 3.5.2)
Installed from:    Ubuntu Packages
Compiler:          gcc 4.0.2 
OS:                Linux

I have a Dell Axim X51v, I recieve files by OBEX with KDE OBEX push server ok.

When I send files by OBEX to Ubuntu if the file is less than 1 kb all is ok, but
if size is greater than 1 kb KDE OBEX push server for Bluetooth crash and cause the signal 6 (SIGABRT)

Backtrace:

Using host libthread_db library "/lib/tls/i686/cmov/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)
(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 -1231337792 (LWP 11683)]
(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)
(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)
[KCrash handler]
#9  0xffffe410 in ?? ()
#10 0xbf99d3b4 in ?? ()
#11 0x00000006 in ?? ()
#12 0x00002da3 in ?? ()
#13 0xb6a159d1 in raise () from /lib/tls/i686/cmov/libc.so.6
#14 0xb6a172e9 in abort () from /lib/tls/i686/cmov/libc.so.6
#15 0xb6a4970a in __fsetlocking () from /lib/tls/i686/cmov/libc.so.6
#16 0xb6a4ff74 in malloc_trim () from /lib/tls/i686/cmov/libc.so.6
#17 0xb6a51891 in free () from /lib/tls/i686/cmov/libc.so.6
#18 0xb6a52a86 in realloc () from /lib/tls/i686/cmov/libc.so.6
#19 0xb7f78167 in g_netbuf_realloc () from /usr/lib/libopenobex-1.0.so.0
#20 0xb7f7822d in g_netbuf_put () from /usr/lib/libopenobex-1.0.so.0
#21 0xb7f75626 in obex_data_indication () from /usr/lib/libopenobex-1.0.so.0
#22 0xb7f76aa4 in obex_transport_handle_input ()
   from /usr/lib/libopenobex-1.0.so.0
#23 0xb7f74b03 in OBEX_HandleInput () from /usr/lib/libopenobex-1.0.so.0
#24 0x0805b812 in Obex_handleEvent ()
#25 0x0805ba43 in Obex_handleEvent ()
#26 0x0805c290 in ObexBluetooth::staticMetaObject ()
#27 0xb71c4929 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#28 0xb71c5238 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#29 0xb7524c67 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#30 0xb71e4faa in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#31 0xb715bf80 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#32 0xb715c172 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#33 0xb78a817c in KApplication::notify () from /usr/lib/libkdecore.so.4
#34 0xb70ecdb7 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#35 0xb714dacb in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#36 0xb7100a60 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#37 0xb7173cfb in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#38 0xb7173c1e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#39 0xb715ac13 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#40 0x0805402c in ?? ()
#41 0xbf99dfb8 in ?? ()
#42 0x08112668 in ?? ()
#43 0x00000011 in ?? ()
#44 0xbf99e0d0 in ?? ()
#45 0x00000000 in ?? ()
#46 0x00000001 in ?? ()
#47 0x0805da2f in vtable for QGList ()
#48 0x00000000 in ?? ()
#49 0x00000000 in ?? ()
#50 0x0805da1b in vtable for QGList ()
#51 0xfffffff0 in ?? ()
#52 0xbf99dfb8 in ?? ()
#53 0xb6a523b1 in malloc () from /lib/tls/i686/cmov/libc.so.6
#54 0xb6a01ec2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#55 0x08053d81 in ?? ()

hciconfig hci0:
hci0:   Type: USB
        BD Address: 00:80:5A:46:02:9B ACL MTU: 384:8 SCO MTU: 64:8
        UP RUNNING PSCAN ISCAN
        RX bytes:19654 acl:235 sco:0 events:533 errors:0
        TX bytes:5206 acl:201 sco:0 commands:244 errors:0
lsbus:
Bus 004 Device 019: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Comment 1 Christoph Feck 2011-12-20 02:58:11 UTC
This crash report is at least 4 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in KDE 4 or the backtrace is no longer applicable to KDE 4.

If the crash still happens with a recent KDE version (4.7.4 or 4.8), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or NEW)
Comment 2 Andrew Crouthamel 2018-09-04 18:11:17 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.