Since the tool is in its nascent stages, I reported only a handful of
reports that I myself looked at felt that they were potentially bugs.
I appreciate everyone's feedback.
Best,
Ted
On May 2, 2004, at 4:50 PM, Tom Lane wrote:
Neil Conway <[EMAIL PROTECTED]> writes:
The problem with applying thi
Neil Conway <[EMAIL PROTECTED]> writes:
> The problem with applying this kind of static analysis to PostgreSQL is
> that palloc() is not like malloc(): if the return value goes out of
> scope before it is freed, it is NOT necessarily the case that a memory
> leak has occurred.
I'm a bit surpris
Thanks Neil. The information about palloc() is extremely useful, and
it will be interesting for us to see how our analysis can better deal
with this.
Thanks for the quick reply!
Best,
Ted
On May 2, 2004, at 12:23 PM, Neil Conway wrote:
On 2-May-04, at 2:05 PM, Ted Kremenek wrote:
I'm from the S
On 2-May-04, at 2:05 PM, Ted Kremenek wrote:
I'm from the Stanford Metacompilation research group where we use
static analysis to find bugs.
Neat. BTW, I saw a talk last summer from Madanlal Musuvathi on some
model checking work which I believe is being done by a related group at
Stanford; it wa
Sorry if this is a repeat. I checked the mailing list archive and this
message didn't show up, so I am reposting it.
Hi,
I'm from the Stanford Metacompilation research group where
