ChristosH wrote:
> Alan, you said 1.1.6 will be addressing this specific issue, or is it
> something I should continue looking into?
There is a known double free in 1.1.5 that will be fixed in 1.1.6.
That should be released this week.
> Do you have a schedule posted for 2.0.0.
Soon. At this
rough VMWare!)
Alan, you said 1.1.6 will be addressing this specific issue, or is it
something I should continue looking into? Do you have a schedule posted for
2.0.0.
--
View this message in context:
http://www.nabble.com/double-free-or-corruption-errors-with-2.0.0-pre0-tf3538902.html#a9924881
matthew zeier wrote:
> I find that hard to believe since google found a number of hits
> (http://tinyurl.com/2daram is a good example)
Which is in 1.1.5. I have already told you multiple times that it's
known, and will be fixed in 1.1.6. Please read my messages.
What *isn't* known is a dou
Alan DeKok wrote:
> matthew zeier wrote:
>> Doesn't dump core so all I got was:
>
> As you posted before.
>
> Let me clear: I cannot reproduce this problem here. No one else has
> seen the same problem.
I find that hard to believe since google found a number of hits
(http://tinyurl.com/2
matthew zeier wrote:
> Doesn't dump core so all I got was:
As you posted before.
Let me clear: I cannot reproduce this problem here. No one else has
seen the same problem.
One inescapable conclusion is that your machine has the information as
to what the problem is.
Another inescapable
Alan DeKok wrote:
> matthew zeier wrote:
>> How would I know where the double free is? Just running 'radiusd -X' spit
>> out
>> that error just before failing to run.
>
> As I said before: doc/bugs
>
Doesn't dump core so all I got was:
Starting program: /usr/local/sbin/radiusd
[Thread de
matthew zeier wrote:
> How would I know where the double free is? Just running 'radiusd -X' spit
> out
> that error just before failing to run.
As I said before: doc/bugs
It contains "documentation" that may help. It's pointed to from the
web page, and other places.
>> Yes. That's fix
Alan DeKok wrote:
> matthew zeier wrote:
>> What sort of additional information would be useful?
>
> doc/bugs
>
> i.e. WHERE the double free is. The message you showed says "something
> went wrong.". That's nice. Which line of code needs to be changed?
How would I know where the double
matthew zeier wrote:
> What sort of additional information would be useful?
doc/bugs
i.e. WHERE the double free is. The message you showed says "something
went wrong.". That's nice. Which line of code needs to be changed?
Changing a line at random won't help. Hence the need to know whe
What sort of additional information would be useful? If it matters, I was
having the same problem with 1.1.5.
Alan DeKok wrote:
> matthew zeier wrote:
>> Grabbed 2.0.0-pre0 from CVS (the latest, I presume) on a RHEL4 system
>> with perl 5.8.8.
>>
>> Running /usr/local/sbin/radiusd -X gives:
>>
matthew zeier wrote:
> Grabbed 2.0.0-pre0 from CVS (the latest, I presume) on a RHEL4 system
> with perl 5.8.8.
>
> Running /usr/local/sbin/radiusd -X gives:
>
> radiusd: entering modules setup
> Module: Library search path is /usr/lib
> modules: Not loading pre-proxy{} section
> modules: Not l
Grabbed 2.0.0-pre0 from CVS (the latest, I presume) on a RHEL4 system
with perl 5.8.8.
Running /usr/local/sbin/radiusd -X gives:
radiusd: entering modules setup
Module: Library search path is /usr/lib
modules: Not loading pre-proxy{} section
modules: Not loading post-proxy{} section
*** glibc
12 matches
Mail list logo
