NNTPC: One 'memory currupt' fixed + caching question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



sthaug@nethelp.no wrote:
> 
> Looking at the DoIPC() routine, we see that it free()s the val
> pointer returned from hisGetDbz(). But the pointer is a static in
> hisGetDbz(), and is also free()d there at line 130 if non-NULL.

No.  The pointer variable is static in hisGetDbz, but the actual string pointed
to is not static.  So the frees are correct.
 
> And after this change, it seems to run very nice and stable, without
> the 'Memory currupt' problems.

It's probably a coincidence.

> Now for a question. If I access an article by article number within a
> group, it is read from the upstream feed the first time, and returned
> from the cache if I access the same article number again. On the other
> hand, if I access the same article by message ID, it is read from the
> upstream feed every time:

Seems to be a sign of history "corruption".  I'll look into it.

-- 
Debian GNU/Linux 1.2 is out! { http://www.debian.org/ }
Email:  Herbert Xu ~{PmV>HI~} <herbert@greathan.apana.org.au>
{ http://greathan.apana.org.au/~herbert/ }
PGP Key:  pgp-public-keys@pgp.mit.edu or any other key sites


[Index of Archives]     [Yosemite]     [Yosemite Campsites]     [Bugtraq]     [Linux]     [Trn]

Powered by Linux