#680 closed defect (fixed)
chicken HEAD (2011-08-31) breaks sedna
| Reported by: | Mario Domenech Goulart | Owned by: | felix winkelmann |
|---|---|---|---|
| Priority: | major | Milestone: | 4.9.0 |
| Component: | unknown | Version: | 4.7.x |
| Keywords: | sedna | Cc: | |
| Estimated difficulty: |
Description
See http://tests.call-cc.org/master/linux/x86/2011/08/31/salmonella-report/sedna.html
The day before it was not failing (http://tests.call-cc.org/master/linux/x86/2011/08/30/salmonella-report/sedna.html).
It's possible that it is a sedna bug (I haven't checked it). Just in case, I'm opening this ticket.
Change History (5)
comment:1 Changed 14 years ago by
comment:2 Changed 13 years ago by
| Owner: | set to felix winkelmann |
|---|---|
| Status: | new → assigned |
comment:3 Changed 13 years ago by
This was caused by an optimization rule for call-with-values which was incorrectly triggered due to a bug in the scrutinizer.
comment:4 Changed 13 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Could this be because sedna:extract-string is supposed to return 2 values, but one of the conditional branches returns #f after raising a continuable exception, confusing the flow analysis? Perhaps it should return (values #f #f) or signal a non-continuable exception instead (will the flow analysis understand that?)