Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
We now leak less than 1 MB on
valgrind --leak-check=full eeshow -N 1 neo900.pro -- png -o foo.png
instead of about 3.5 MB.
The plan is as follows:
- fix memory leaks in simple operations in on-interactive mode,
- suppress what cannot be fixed (e.g., when comes from libraries),
- move on to more complex operations,
- then start fixing interactive mode.
|
|
|
|
In the index, we don't want to have pages marked because there's a
page underneath that has changed. After all, that other page is
being shown in the index as well.
However, in all other cases we still want to recurse.
|
|
|
|
The days of only doing FIG are long gone ...
|
|
|
|
|
|
|
|
This means that we can now do things like
eeshow 6a9f71:neo900.pro neo900_SS_5.sch -- \
diff -s 2 -o diff.png neo900.pro neo900_SS_5.sch
|
|
This prevents problems in case the argument list disappears, and
one doesn't have to distinguish freeing of file_names initialized
with classify_files from freeing of file_names returned by
pro_parse_file.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Finally ! Shoulds have done this a long time ago.
|
|
|
|
|
|
|
|
We don't really need to, but valgrind complains about it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We currently only do lines, no text.
|
|
|
|
|
|
|
|
|
|
|
|
We use "return" quite a lot, which isn't what one would want in that loop.
|