#1765: Memory leak in allocate_interpreter
-----------------------+----------------------------------------------------
Reporter: nwellnhof | Owner: bluescreen
Type: bug | Status: assigned
Priority: normal | Milestone:
Component: core | Version: trunk
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
-----------------------+----------------------------------------------------
Comment(by bluescreen):
I agree that freeing a null pointer doesn't give you anything. I think its
the way valgrind works it just sees that you're not doing anything with a
chunk of memory recently allocated - meaning not freeing it, not returning
it - for the branch of (!ptr && size).
Without the patch I was able to reproduce your original report in which
valgrind reported "definitely lost" blocks.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1765#comment:5>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
