Bug 160318 - Konsole crashes when bash in one of its tabs crashes
Summary: Konsole crashes when bash in one of its tabs crashes
Status: RESOLVED REMIND
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 1.6
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-03 13:25 UTC by Tomer Shalev
Modified: 2008-06-01 09:11 UTC (History)
0 users

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 Tomer Shalev 2008-04-03 13:25:07 UTC
Version:           1.6 (using KDE 3.5.8)
Installed from:    Debian testing/unstable Packages
OS:                Linux

I've created two tabs with a bash console.
I managed to crash Bash (which is very difficult to do...) by using fdisk on a defective USB Mass Storage devices.
This cause fdisk to crash, and crashed Konsole as well (?!).

I guess Bash crashes as a result of fdisk crashing.

Does Konsole sustain a crash in Bash?
In order to reproduce and test this scenario, one needs to have a way to crash the shell which Konsole uses in a particular tab, then test whether Konsole sustain that crash.
Comment 1 Robert Knight 2008-04-03 17:38:38 UTC
> In order to reproduce and test this scenario, one needs to have a way to
> crash the shell which Konsole uses in a particular tab, then test
> whether Konsole sustain that crash. 

That can be done easily, just stop bash using "kill" with signal number 11 (SIGSEGV, which is the signal usually sent when an application crashes).

I couldn't reproduce this here (the Konsole tab holding the killed session just closes) and without a backtrace from Konsole there is not a lot I can do.

When Konsole crashes and the KDE crash dialog appears, please go to the Backtrace tab and copy the contents into the bug report.
Comment 2 Robert Knight 2008-04-03 17:39:28 UTC
> just stop bash using "kill" with signal number 11 

kill -s 11 <pid>

(Where <pid> is the process id of bash)
Comment 3 Robert Knight 2008-04-15 14:28:00 UTC
Can you reproduce this?  If so, please attach the backtrace to the report.
Comment 4 Tomer Shalev 2008-04-15 17:04:41 UTC
I will do so in a couple of days (out of office)
Comment 5 Robert Knight 2008-05-23 22:23:59 UTC
Closing as 'remind' for now until more information is available. 
Comment 6 Tomer Shalev 2008-06-01 09:11:44 UTC
I've tried your suggestion from comment #2 (kill -s 11 <pid>).
The bug does not occur. This is probably an INVALID bug, and you can close it.