fork_exec_with_pipes creates a new process kde4-config.
scite obviously gets a signal (which signal?) when this
new process terminates (?) and fails in the signal handling
with SIGSEGV. This explains why the stack below
IA__g_spawn_sync is not always the same (sometimes
the crash comes a little later).
There seem to be other packages affected by the same kind of
bug, just look for fork_exec_with_pipes.
Can be reproduced with karmic and kde netbook desktop.
No crash occurs with gnome.
Call stack:
<signal_ handler_ called> with_pipes (glib2. 0-2.22. 3/glib/ gspawn. c:1199)
fork_exec_
IA__g_spawn_sync
fork_exec_ with_pipes creates a new process kde4-config.
scite obviously gets a signal (which signal?) when this
new process terminates (?) and fails in the signal handling
with SIGSEGV. This explains why the stack below
IA__g_spawn_sync is not always the same (sometimes
the crash comes a little later).
There seem to be other packages affected by the same kind of with_pipes.
bug, just look for fork_exec_