Bug 326191 – Crash when pressing Ctrl+C from terminal

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 326191 - Crash when pressing Ctrl+C from terminal


Summary:	Crash when pressing Ctrl+C from terminal


Status:	RESOLVED FIXED

Product:	gedit
Classification:	Applications
Component:	general
Version:	git master
Hardware:	Other Linux

Importance:	Normal blocker
Target Milestone:	---
Assigned To:	Gedit maintainers
QA Contact:	gedit QA volunteers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-01-08 11:14 UTC by Paolo Maggi
Modified:	2006-01-08 21:57 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
This patch should fix the reported crash (2.33 KB, patch) 2006-01-08 14:47 UTC, Paolo Maggi	committed	Details \| Review

Description Paolo Maggi 2006-01-08 11:14:43 UTC

I have just had a crash pressing Ctrl+C from terminal.
Jesse had the same problem yesterday.

On the terminal I got:

paolo@elilix:/gnome/gnome-214/cvs/gedit/gedit$ gedit

Exception exceptions.KeyboardInterrupt in 'garbage collection' ignored
Fatal Python error: unexpected exception during garbage collection


Backtrace here:

Backtrace was generated from '/opt/gnome/gnome-214/INSTALL/bin/gedit'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1225496896 (LWP 14581)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 65036

Thread 1 (Thread -1225496896 (LWP 14581))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 784

Comment 1 Paolo Maggi 2006-01-08 12:02:10 UTC

jessevdk paolo: the Ctrl-C problem might be fixable by not allowing python to handle SIGINT

Comment 2 Paolo Maggi 2006-01-08 14:46:25 UTC

jessevdk: hmm, putting: signal(SIGINT, SIG_DFL); after Py_Initialize() fixes all Ctrl-C problems
kikidonk: paoloLUNCH: well yes i think jesse is right

Comment 3 Paolo Maggi 2006-01-08 14:47:22 UTC

Created attachment 56968 [details] [review]
This patch should fix the reported crash

Patch based on the Jesse's suggestion.

Comment 4 Paolo Maggi 2006-01-08 21:57:44 UTC

Committed to CVS HEAD.