iv-m (Ivan Melnikov)
- Login: iv-m
- Email: iv@altlinux.org
- Registered on: 09/26/2019
- Last sign in: 09/26/2019
Issues
open | closed | Total | |
---|---|---|---|
Assigned issues | 0 | 0 | 0 |
Reported issues | 0 | 1 | 1 |
Activity
09/27/2019
- 10:05 AM Ruby master Bug #16184: Entry persists in catch table even though its labels were removed, which may cause [BUG]
- > And having `position` field of labels initialized (as in my attached patch) makes crash totally impossible.
I th... - 09:33 AM Ruby master Bug #16184 (Open): Entry persists in catch table even though its labels were removed, which may cause [BUG]
- > So whether Ruby crashes or not depends on the contents of the memory where labels are allocated by compile_rescue f...
- 09:30 AM Ruby master Bug #16184: Entry persists in catch table even though its labels were removed, which may cause [BUG]
- > Could you post a reproducer that reliably crashes Ruby?
I guess this is not really possible to crash Ruby reliab...
09/26/2019
- 01:22 PM Ruby master Bug #16184: Entry persists in catch table even though its labels were removed, which may cause [BUG]
- Of course, while having some strange cache table entries would be pretty ok if they were not used (like it usually ha...
- 01:18 PM Ruby master Bug #16184 (Closed): Entry persists in catch table even though its labels were removed, which may cause [BUG]
- When `remove_unreachable_chunk` removes the code from within a rescue block, the catch table entry corresponding the ...
Also available in: Atom