[isf-wifidog] output

[Clifford Thurber]

Ok. So set that variable and then restart wifidog?

On Tue, Jul 29, 2008 at 3:11 PM, acv <acv at miniguru.ca> wrote:

>        Well, I'm at work right now so I don't have access to a box where
> I can trash the firewall at will. If you can provide me a temp account with
> root, I might be able to debug this now, otherwise it will have to wait.
>
> Work around is to disable error checking in glibc:
>
> In BASH:
>
> export MALLOC_CHECK_=0
>
> In CSH:
>
> setenv MALLOC_CHECK_=0
>
> Alex
>
> On Tue, Jul 29, 2008 at 02:36:24PM -0400, Clifford Thurber wrote:
> > Date: Tue, 29 Jul 2008 14:36:24 -0400
> > From: "Clifford Thurber" <clifford at hdn.net>
> > To: "WiFiDog Captive Portal" <wifidog at listes.ilesansfil.org>
> > Subject: Re: [isf-wifidog] output
> >
> > Interesting. Can I provide you with anything else that might help you?
> >
> > Thanks
> > Clifford
> >
> > On Tue, Jul 29, 2008 at 2:32 PM, acv <acv at miniguru.ca> wrote:
> >
> > > On Tue, Jul 29, 2008 at 01:41:04PM -0400, Clifford Thurber wrote:
> > > > Date: Tue, 29 Jul 2008 13:41:04 -0400
> > > > From: "Clifford Thurber" <clifford at hdn.net>
> > > > To: acv at miniguru.ca
> > > > Subject: output
> > > >
> > > > Hi Alex,
> > > > This is what I am seeing now:
> > > >
> > > [ ... snip ... ]
> > > > called. Trying to reap a child
> > > > [7][Mon Jul 28 14:47:27 2008][26253](gateway.c:263) Handler for
> SIGCHLD
> > > > reaped child PID -1
> > > > [7][Mon Jul 28 14:47:27 2008][26253](util.c:121) Process PID 26358
> exited
> > > > [7][Mon Jul 28 14:47:27 2008][26253](centralserver.c:327) Level 1:
> > > > Connecting to auth server auth.ilesansfil.org:80
> > > > *** glibc detected *** wifidog: free(): invalid pointer:
> > > 0x0000003ea656a0c0
> > > > ***
> > > > ======= Backtrace: =========
> > > > /lib64/libc.so.6[0x3ea6278158]
> > > > /lib64/libc.so.6(cfree+0x76)[0x3ea627a796]
> > > > wifidog[0x4081ef]
> > > > wifidog[0x407d35]
> > > > wifidog[0x40baab]
> > >
> > > Congratulations, you found a hidden bug. Most versions of libc silently
> > > ignore when an application tries to free() memory that's already been
> > > free()'d. Gentoo, Ubuntu and apparently now Fedora have started
> enabling
> > > optional behaviour in the free() system call to exit out when that
> happens.
> > > This was originally implemented for debugging purpose.
> > >
> > > Now we have to find where free() gets called twice... Probably when
> > > connecting
> > > to the Auth Server.
> > >
> > > Alex
> > >
>
> > _______________________________________________
> > WiFiDog mailing list
> > WiFiDog at listes.ilesansfil.org
> > http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>
> _______________________________________________
> WiFiDog mailing list
> WiFiDog at listes.ilesansfil.org
> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://listes.ilesansfil.org/pipermail/wifidog/attachments/20080729/8f2e2299/attachment.htm