attached.
Joris Huizer wrote:
Segin wrote:
Attached is version 0.2 of this script, with a lot of additional
functionality. You will need to be able to write to /tmp and make a
file /tmp/grep to use the extended functionality (default
functionality needs none of that, and is unmodified.)
Segin wrote:
Attached is version 0.2 of this script, with a lot of additional
functionality. You will need to be able to write to /tmp and make a file
/tmp/grep to use the extended functionality (default functionality needs
none of that, and is unmodified.)
Your message does not have the sc
Attached is version 0.2 of this script, with a lot of additional
functionality. You will need to be able to write to /tmp and make a file
/tmp/grep to use the extended functionality (default functionality needs
none of that, and is unmodified.)
For those that are intested, you can fetch memche
Jim White wrote:
Joris Huizer wrote:
Segin wrote:
It's not a C interpeter, it's literally a frint end of sorts to
grep. There's only one textual occurence of malloc() in the code, so
it only returns one.
Think before you speak.
P.S. I'll add a C interpeter when there becomes a need for o
That's ok, I failed to document that myself. In truth, it would
truthfully be inpossible to find run-time memory leaks like that using a
script because of a potential unknown variable in a for loop which is
derived from an argument or return from another function.
I will try to add code for de
Joris Huizer wrote:
Segin wrote:
It's not a C interpeter, it's literally a frint end of sorts to grep.
There's only one textual occurence of malloc() in the code, so it only
returns one.
Think before you speak.
P.S. I'll add a C interpeter when there becomes a need for one.
It was my im
Segin wrote:
It's not a C interpeter, it's literally a frint end of sorts to grep.
There's only one textual occurence of malloc() in the code, so it only
returns one.
Think before you speak.
P.S. I'll add a C interpeter when there becomes a need for one.
It was my impression that the goal
It's not a C interpeter, it's literally a frint end of sorts to grep.
There's only one textual occurence of malloc() in the code, so it only
returns one.
Think before you speak.
P.S. I'll add a C interpeter when there becomes a need for one.
Joris Huizer wrote:
Segin wrote:
As my small con
Segin wrote:
As my small contribution, attached is a small shell script that,
unmodified, finds out how many times certain functions are called in a
given sample of files. The default functions are 'malloc', 'realloc',
and 'free', and the sample files are all files ending in .c in the
current
As my small contribution, attached is a small shell script that,
unmodified, finds out how many times certain functions are called in a
given sample of files. The default functions are 'malloc', 'realloc',
and 'free', and the sample files are all files ending in .c in the
current directory. It
10 matches
Mail list logo
