#550: t/pmc/codestring.t failing
-------------------------+--------------------------------------------------
Reporter: whiteknight | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: core | Version: trunk
Severity: high | Keywords: codestring pmc icu
Lang: | Patch:
Platform: linux |
-------------------------+--------------------------------------------------
Comment(by Infinoid):
Replying to [comment:7 jkeenan]:
> So, are there people/machines that are still getting a failure on this
file? If not, then can we close the ticket?
I don't know whether anyone else has been able to reproduce it after the
workaround; I haven't heard of any more failures, so we're probably good.
As to whether or not the ticket can be closed, I suppose it depends on
whether this function only processes symbol names internally, or if its
data comes directly from user applications. If it's an internal function
and there's no chance of being passed bad data, the ticket can be closed,
otherwise we should probably do some input filtering (for "parrot should
never segfault" reasons).
I'm not familiar enough with this part of parrot to know how externally
accessible this code is.
Mark
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/550#comment:8>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
