summaryrefslogtreecommitdiff
path: root/Porting/leakfinder.pl
Commit message (Collapse)AuthorAgeFilesLines
* leakfinder.pl: exceptionsFather Chrysostomos2012-12-151-3/+8
|
* leakfinder.pl: More exceptionsFather Chrysostomos2012-12-121-0/+2
|
* leakfinder.pl: Skip push/unshift after { or (Father Chrysostomos2012-12-081-6/+1
|
* leakfinder.pl: Fix select skipFather Chrysostomos2012-12-081-1/+1
| | | | | It wasn’t skipping select without parentheses, which was the purpose of that (?:...) group.
* leakfinder: More exceptionsFather Chrysostomos2012-11-171-1/+29
|
* leakfinder.pl: More exceptionsFather Chrysostomos2012-11-151-6/+14
|
* leakfinder.pl: Run evals four timesFather Chrysostomos2012-11-151-1/+1
| | | | With three times we still get false positives
* leakfinder.pl: More exceptionsFather Chrysostomos2012-11-151-0/+5
|
* leakfinder.pl: Duh!Father Chrysostomos2012-11-141-1/+1
| | | | I hadn’t tested this before I committed it. It had a syntax error.
* leakfinder.pl: more exceptionsFather Chrysostomos2012-11-131-0/+2
|
* leakfinder.pl: More exceptionsFather Chrysostomos2012-11-131-0/+3
|
* leakfinder.pl: More exceptionsFather Chrysostomos2012-11-131-0/+4
|
* leakfinder.pl: Run code more timesFather Chrysostomos2012-11-131-1/+1
| | | | | | Sometimes a piece of code will still create new SVs on the second or even the third iteration, but not after that. That doesn’t count as a leak.
* leakfinder.pl: Many more exceptionsFather Chrysostomos2012-11-111-1/+55
|
* leakfinder.pl: Yet mair exceptionsFather Chrysostomos2012-11-081-2/+3
|
* leakfinder.pl: Clean up exceptionsFather Chrysostomos2012-11-061-14/+4
| | | | | | | | | Remove two (exit and END) that were from preliminary versions of the script. Skip all lines beginning with push and unshift. Remove leading whitespace when looking up exceptions.
* leakfinder.pl: Another exceptionFather Chrysostomos2012-11-061-0/+1
|
* leakfinder.pl: Mair exceptionsFather Chrysostomos2012-11-041-1/+9
|
* leakfinder.pl: Show file namesFather Chrysostomos2012-11-041-0/+1
| | | | | It can take a *very* long time to run, so give some indication that it is actually doing something.
* leakfinder.pl: Use DD for outputFather Chrysostomos2012-11-041-4/+6
| | | | | This solves the problem of binary code being dumped into the terminal.
* leakfinder.plFather Chrysostomos2012-11-041-0/+57
I wrote this to look for memory leaks. Since it could be useful to re-run it at some future time, I might as well put it somewhere where it will not get lost. It still needs a bit of work. Currently, evaluating chunks of binary code can cause memory leaks. In those cases the binary code is dumped straight to the terminal, which is not helpful.