Thanks Alan for your prompt reply.
Judy worked perfectly fine for me with 32 bit compilation.
This is the first time i am compiling it for 64 bit on solaris. So wanted to
check if somebody has already compiled and using it on 64 bit platform.
I have also checked with UMEM and i found no leaks with 32 bit libraries, but
with 64 bit it shows heap corruption. Also tried changing offset variable
(which is declared as int) in Judy1Set.c to Word_t. It fixed the issue but the
final results (bit counts) are not OK.
Regards,
Atul Shridhar
________________________________
From: Alan Silverstein <[email protected]>
To: [email protected]; [email protected]
Sent: Wednesday, 29 July, 2009 2:12:29 AM
Subject: Re: 64bit Judy library issue
Atul et al, no idea, hoping Doug or someone else will come forth with
an answer. I can tell you libJudy has never had a memory problem (at
least not the original 2002 version in SourceForge), and when using it
recently at a job, I ran Purify on it and it was clean, other than a
weird non-bug having to do with how it handles irrelevant bits in bytes.
Any chance you have a bad malloc() library?
Alan Silverstein
Love Cricket? Check out live scores, photos, video highlights and more.
Click here http://cricket.yahoo.com------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Judy-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/judy-devel
