Custom Query (132 matches)
Results (25 - 27 of 132)
|#32||fixed||patch to make libyaml compile in visual studio||xi||roel _ dot _ vanhout _ at _ gmail _ dot _ com|
|#35||worksforme||test program crashes on test file with multiple documents||xi||roel _ dot _ vanhout _ at _ gmail _ dot _ com|
The run-parser.c test file crashes on the following test document: ============START================
--- - Harry Potter and the Prisoner of Azkaban - Harry Potter and the Goblet of Fire - Harry Potter and the Order of the Phoenix --- - Memoirs Found in a Bathtub - Snow Crash - Ghost World
Crash in is api.c, line 604 of the release tarball:
When I comment out the second document of the test file (from the second '---' on down), it runs fine.
|#157||invalid||pyyaml-3.09 dumps core||xi||rich@…|
I'm not sure how to provide a small demonstration here.
In the "spread" module, (SpreadModule? on pypi), there is a type spread.MembershipMsg? which contains a "group_id", spread.MembershipMsg?.group_id. The group_id is an opaque type. I'm not sure how to generate one of these easily aside from bringing up a spread system, which seems like overkill.
In any case, attempting to serialize this opaque type with pyyaml results in a python core dump.
I recognize that pyyaml can't possibly know how to serialize or unserialize this sort of object. However, I think that attempting to do so should result in a suitable exception rather than an interpreter core dump.
I'll find another way around my problem. But chasing down this dump took me a couple of days. If it had been an exception, I'd have found the problem in minutes.