Bug 1225880 - Calling nil as a function in SBCL causes a memory fault
Summary: Calling nil as a function in SBCL causes a memory fault
Status: RESOLVED UPSTREAM
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Development (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-03 19:08 UTC by Yaroslav Khnygin
Modified: 2024-06-03 22:12 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Reproduction log (1.28 KB, text/x-log)
2024-06-03 19:08 UTC, Yaroslav Khnygin 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yaroslav Khnygin 2024-06-03 19:08:51 UTC 
Created attachment 875283 [details]
Reproduction log

Calling nil as a function in sbcl reliably causes a memory fault.

Steps to reproduce:
1. Run sbcl
2. Type (nil) and press Enter.
See the attached log.

Actual result: sbcl reports an unhandled memory fault at #x0.

Expected result: sbcl reports an undefined-function error.

Builds SBCL 2.4.4-1.1-suse and 2.4.5-1.1-suse.

This issue is not reproducible in a build of the upstream repository, e.g. SBCL 2.4.5.37-0ac37eafc, so it has to be specific to openSUSE.
Comment 1 Yaroslav Khnygin 2024-06-03 20:24:58 UTC 
I was wrong about the bug being specific to openSUSE, I managed to reproduce the bug in upstream 2.4.5. It has been fixed in a commit after 2.4.5: https://github.com/sbcl/sbcl/commit/eb980c41474708df03e6188b9b32986bdd8266e5
Comment 2 Yaroslav Khnygin 2024-06-03 22:12:16 UTC 
See the previous comment.