|
Bugzilla – Full Text Bug Listing |
| Summary: | Calling nil as a function in SBCL causes a memory fault | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Yaroslav Khnygin <yaroslav.hnygin> |
| Component: | Development | Assignee: | E-mail List <screening-team-bugs> |
| Status: | RESOLVED UPSTREAM | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE Tumbleweed | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Reproduction log | ||
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 See the previous comment. |
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.