Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ansi-test
ansi-test
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 6
    • Merge Requests 6
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ansi-test
  • ansi-testansi-test
  • Issues
  • #29

Closed
Open
Created Dec 30, 2020 by Michał Herda@mherda🤔Contributor

Add tests for calling readers/writers with invalid argument count

(defclass foo () ((name :reader foo-name)))
(foo-name (make-instance 'foo) #'print)

This should signal a program-error but instead causes a segfault on SBCL 2.1.0 and earlier on default optimization settings. I think that ANSI-TEST could use a few regression tests that cover these cases.

This wasn't caught earlier, e.g. by CELL-ERROR-NAME.ERROR.2, because conditions are not standard-objects on SBCL.

Discovered by running the Portable Condition System test suite, adapted from ANSI-TEST.

Edited Dec 30, 2020 by Michał Herda
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None