Bug 43097 - kdat crashes while trying to mount a probably unreadable tape
Summary: kdat crashes while trying to mount a probably unreadable tape
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kdat
Classification: Miscellaneous
Component: general (show other bugs)
Version: 2.0.1
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: needs_verification
Depends on:
Blocks:
 
Reported: 2002-05-26 13:03 UTC by J Reitsma
Modified: 2009-08-26 15:32 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description J Reitsma 2002-05-26 12:54:57 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kdat
Version:           2.0.1 (using KDE 3.0.0 )
Severity:          normal
Installed from:    SuSE
Compiler:          gcc version 2.95.3 20010315 (SuSE)
OS:                Linux (i686) release 2.4.10-4GB
OS/Compiler notes: 

I loaded a tape in the drive with probably was unreadable: the 'dd -if' command on the tape gave a
'Could not allocate memory'-error

(mesaage originally in Dutch by the way).

When I try to mount that tape with kdat it crashes with a 'segmentation fault'. The option 'Abort' says to give a dump but I could not find that.

The following info I gathered from .xsession-errors' and KDE's backtrack:

kdat: SIGSEGV signal ("Segmentation violation (ANSI)") caught
kdat: SIGSEGV signal ("Segmentation violation (ANSI)") caught
WARNING: KDE detected X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  42
KCrash: crashing.... crashRecursionCounter = 2
KCrash: Application Name = kdat path = <unknown> pid = 9233cd


0x40fc9079 in ?? ()
#0  0x40fc9079 in ?? ()
#1  0x40e56177 in ?? ()
#2  0x405da5bc in ?? ()
#3  0x40e53bc4 in ?? ()
#4  <signal handler called>
#5  0x40f4f861 in ?? ()
#6  0x40e53fd6 in ?? ()
#7  0x40f50c81 in ?? ()
#8  0x080644f4 in ?? ()
#9  0x40e53bc4 in ?? ()
#10 <signal handler called>
#11 0x4086fda1 in ?? ()
#12 0x4086fc44 in ?? ()
#13 0x40551e15 in ?? ()
#14 0x408f5426 in ?? ()
#15 0x4086fda6 in ?? ()
#16 0x4086fc44 in ?? ()
#17 0x40551e15 in ?? ()
#18 0x408f5426 in ?? ()
#19 0x4096b5f0 in ?? ()
#20 0x409d1bc5 in ?? ()
#21 0x403a7144 in ?? ()
#22 0x4086fda6 in ?? ()
#23 0x4086fc44 in ?? ()
#24 0x40551e15 in ?? ()
#25 0x408f5426 in ?? ()
#26 0x4086fda6 in ?? ()
#27 0x4086fc44 in ?? ()
#28 0x40551e15 in ?? ()
#29 0x408f5426 in ?? ()
#30 0x409a3cd1 in ?? ()
#31 0x4086fda6 in ?? ()
#32 0x4086fc44 in ?? ()
#33 0x40551e15 in ?? ()
#34 0x40870a12 in ?? ()
#35 0x4081ec32 in ?? ()
#36 0x4081da36 in ?? ()
#37 0x40871231 in ?? ()
#38 0x40a11ab9 in ?? ()
#39 0x40a339f6 in ?? ()
#40 0x080644b9 in ?? ()
#41 0x40e53bc4 in ?? ()
#42 <signal handler called>
#43 0x408d5792 in ?? ()
#44 0x408914d9 in ?? ()
#45 0x40412d42 in ?? ()
#46 0x409547b3 in ?? ()
#47 0x408f5245 in ?? ()
#48 0x4086fda6 in ?? ()
#49 0x4086fc44 in ?? ()
#50 0x40551e15 in ?? ()
#51 0x4084dab3 in ?? ()
#52 0x40412785 in ?? ()
#53 0x408f5230 in ?? ()
#54 0x4086fda6 in ?? ()
#55 0x4086fc44 in ?? ()
#56 0x40551e15 in ?? ()
#57 0x4081f44d in ?? ()
#58 0x408f42c4 in ?? ()
#59 0x40a12113 in ?? ()
#60 0x40a11aa4 in ?? ()
#61 0x4040c16c in ?? ()
#62 0x4040c65c in ?? ()
#63 0x4040c2b6 in ?? ()
#64 0x0806faae in ?? ()
#65 0x0806db46 in ?? ()
#66 0x08068ff9 in ?? ()
#67 0x408c8785 in ?? ()
#68 0x408c883b in ?? ()
#69 0x4041409d in ?? ()
#70 0x40413b25 in ?? ()
#71 0x40414329 in ?? ()
#72 0x408c8724 in ?? ()
#73 0x408c866e in ?? ()
#74 0x40b7eb0c in ?? ()
#75 0x40954634 in ?? ()
#76 0x408f5081 in ?? ()
#77 0x4086fda6 in ?? ()
#78 0x4086f6e7 in ?? ()
#79 0x40551e15 in ?? ()
#80 0x4082181c in ?? ()
#81 0x4081ed30 in ?? ()
#82 0x4081da36 in ?? ()
#83 0x40871231 in ?? ()
#84 0x4081d99b in ?? ()
#85 0x0808c1e3 in ?? ()
#86 0x40f3e7ee in ?? ()

I run SuSE 7.3 memory some 512 MB

I hope you can do somethin with it of course I'm willing to gieve more info if you need it.

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)
Comment 1 George Goldberg 2007-10-30 05:22:36 UTC
Is this bug still present/relevant in a recent KDE version, such as 3.5.8?
Comment 2 J Reitsma 2007-10-30 22:27:35 UTC
Surprising to see a comment to a bug report this age!

I must say, I don't know at the moment. I don't have the tape-drive installed at the moment, even no scsi-controller present in the systems here. So I'm afraid I can't answer the question, and it would require some serious work to be able to answer it... So, if you really need the answer, I can see what I can do, but not very soon. 

BTW, I still run Suse, 10.3, KDE 3.5.7 at the moment.

regards, Jogchum Reitsma
Comment 3 George Goldberg 2007-10-31 04:51:20 UTC
Almost as surprising to get such a quick response! I will list this bug on the bugsquad* pages as requiring special hardware (DAT drive with a faulty tape), and hopefully someone else with one already set up might be able to verify.

* http://techbase.kde.org/Contribute/Bugsquad/Bugs_to_be_done#Bugs_needing_users_with_particular_setups
Comment 4 FiNeX 2008-11-20 16:19:26 UTC
Added "needs_verification" tag, maybe someone can help us :)
Comment 5 J Reitsma 2008-11-20 22:15:39 UTC
Hmm, I think I should do that, as the OP. But, what I stated a year ago still holds I'm afraid. Even worse, since my mobo (MSI K8N Master2FAR) has some serious trouble, in that the PCI-expressbus doesn't work anymore, and the only pci-slot is occupied by the graphics card. So if someone has that motherboard for me.... ;-)

Hope to find some time for it in the near future...
Comment 6 FiNeX 2009-08-26 15:32:43 UTC
Kdat is not developed and mantained anymore. All Kdat bugs are closed with the status "unmantained".