Summary

sending a SIGQUIT to csi makes it segfault

Metadata

• Id: a6616afab10c69299a6dbd54eae25ba6a1f1b478
• Trac id: 1018
• Type: defect
• Reporter: ckeen
• Owner:
• Cc:
• Status: closed
• Component: unknown
• Estimated difficulty:
• Resolution: wontfix
• Priority: major
• Milestone: someday
• Version: 4.8.x
• Changetime: 2013-06-24 10:14:19 UTC
• Created: 2013-06-21 11:37:16 UTC
• Keywords: csi, segfault, signal handler

Description

This has been reported on chicken-users by Moritz Wilhelmy and Daniel Ajoy.

I can confirm this with a master build.

To reproduce start csi without initialisation of any .csirc (-n), then send it a QUIT signal with kill or type ^\ which does the same thing.

Version 4.8.2 (rev 4e24ed5)

Changes and comments

[2013-06-21 20:06:23 UTC] zbigniew wrote:

I don't seem to be able to reproduce this on OS X (4.7.0.6, 4.8.0.1, 4.8.2), nor on 32 or 64 bit Linux (4.5.2, 4.7.0.6, 4.8.0.1).

[2013-06-24 10:14:19 UTC] ckeen changed status from new to closed

[2013-06-24 10:14:19 UTC] ckeen set resolution to wontfix

[2013-06-24 10:14:19 UTC] ckeen wrote:

I am closing this as it seems that this is not a chicken error at all, see https://lists.nongnu.org/archive/html/chicken-users/2013-06/msg00090.html