lil passes all tests for me on sbcl, ccl, allegro, clisp, but on ecl I get:
Condition of type: SEGMENTATION-VIOLATION Detected access to an invalid or protected memory address.
Which precise test causes the segfault varies at each try.
To reproduce:
rlwrap ecl -eval "'(#.(require "asdf")#.(asdf:test-system :lil))"
:b shows failure either in lil/test/stateful-map::test-stateful-map or in lil/test/pure-map::test-pure-map
and probably at slightly different places therein.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org For followers of most ideologies (openly religious or not), toleration is a concession of defeat. For libertarians, it is victory itself.
Hey,
I have on this testcase:
jack@pandora ~ % rlwrap ecl -eval "'(#.(require "asdf")#.(asdf:test-system :lil))" ;;; Loading "/home/jack/quicklisp/setup.lisp" ;;; Loading #P"/usr/local/lib/ecl-16.1.2/asdf.fas" An error occurred during initialization: Component "reader-interception" not found, required by #<package-inferred-system "lil/test/base">.
Regards, Daniel
Faré writes:
lil passes all tests for me on sbcl, ccl, allegro, clisp, but on ecl I get:
Condition of type: SEGMENTATION-VIOLATION Detected access to an invalid or protected memory address.
Which precise test causes the segfault varies at each try.
To reproduce:
rlwrap ecl -eval "'(#.(require "asdf")#.(asdf:test-system :lil))"
:b shows failure either in lil/test/stateful-map::test-stateful-map or in lil/test/pure-map::test-pure-map
and probably at slightly different places therein.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org For followers of most ideologies (openly religious or not), toleration is a concession of defeat. For libertarians, it is victory itself.
On Thu, Apr 14, 2016 at 1:28 AM, Daniel Kochmański daniel@turtleware.eu wrote:
Hey,
I have on this testcase:
jack@pandora ~ % rlwrap ecl -eval "'(#.(require "asdf")#.(asdf:test-system :lil))" ;;; Loading "/home/jack/quicklisp/setup.lisp" ;;; Loading #P"/usr/local/lib/ecl-16.1.2/asdf.fas" An error occurred during initialization: Component "reader-interception" not found, required by #<package-inferred-system "lil/test/base">.
That's just you missing a dependency. Install all dependencies, or try loading quicklisp instead of requiring asdf.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Thinking is the hardest work there is, which is probably the reason why so few engage in it. — Henry Ford
In fact I did, but it didn't work, so I've tried the testcase you provided with the same result, so I've wrote an e-mail.
I had to manually quickload the reader-interception, because it's not listed in the lil/test dependencies. I think it's a lil's test system definition bug.
Either way, testing the system gives the segmentation-violation just as you said, so the bug is confirmed. I think that it's triggered by something in hu.dwim.stefil (hu.dwim.* already proven a few ECL bugs).
Could you add it to the issue tracker on https://gitlab.com/embeddable-common-lisp/ecl/issues ?
Thanks, Daniel
Faré writes:
On Thu, Apr 14, 2016 at 1:28 AM, Daniel Kochmański daniel@turtleware.eu wrote:
Hey,
I have on this testcase:
jack@pandora ~ % rlwrap ecl -eval "'(#.(require "asdf")#.(asdf:test-system :lil))" ;;; Loading "/home/jack/quicklisp/setup.lisp" ;;; Loading #P"/usr/local/lib/ecl-16.1.2/asdf.fas" An error occurred during initialization: Component "reader-interception" not found, required by #<package-inferred-system "lil/test/base">.
That's just you missing a dependency. Install all dependencies, or try loading quicklisp instead of requiring asdf.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Thinking is the hardest work there is, which is probably the reason why so few engage in it. — Henry Ford
On Thu, Apr 14, 2016 at 10:01 AM, Daniel Kochmański daniel@turtleware.eu wrote:
In fact I did, but it didn't work, so I've tried the testcase you provided with the same result, so I've wrote an e-mail.
I had to manually quickload the reader-interception, because it's not listed in the lil/test dependencies. I think it's a lil's test system definition bug.
I believe the issue might be that quicklisp doesn't play well with package-inferred-system.
Either way, testing the system gives the segmentation-violation just as you said, so the bug is confirmed. I think that it's triggered by something in hu.dwim.stefil (hu.dwim.* already proven a few ECL bugs).
Could you add it to the issue tracker on https://gitlab.com/embeddable-common-lisp/ecl/issues ?
https://gitlab.com/embeddable-common-lisp/ecl/issues/238
Will you be at ELS 2016 in Kraków?
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Fraud is the homage that force pays to reason. — Charles Curtis
Faré writes:
On Thu, Apr 14, 2016 at 10:01 AM, Daniel Kochmański daniel@turtleware.eu wrote:
In fact I did, but it didn't work, so I've tried the testcase you provided with the same result, so I've wrote an e-mail.
I had to manually quickload the reader-interception, because it's not listed in the lil/test dependencies. I think it's a lil's test system definition bug.
I believe the issue might be that quicklisp doesn't play well with package-inferred-system.
Either way, testing the system gives the segmentation-violation just as you said, so the bug is confirmed. I think that it's triggered by something in hu.dwim.stefil (hu.dwim.* already proven a few ECL bugs).
Could you add it to the issue tracker on https://gitlab.com/embeddable-common-lisp/ecl/issues ?
https://gitlab.com/embeddable-common-lisp/ecl/issues/238
Will you be at ELS 2016 in Kraków?
Unfortunately not.
Thanks for adding an issue.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org Fraud is the homage that force pays to reason. — Charles Curtis
-
Daniel Kochmański -
Faré