[Wifidog] Wifidog segfault

David Vincelli micologist at gmail.com
Thu Oct 28 15:13:50 EDT 2004

On Thu, 28 Oct 2004 15:08:52 -0400, Alexandre Carmel-Veilleux
<saruman at northernhacking.org> wrote:
>         When (totalbytes + 1) > MAX_BUF, read gets called with a read
> size of 0. Then read will return 0. 0 <= 0 so the while loop's condition
> is no longer satisfied.

Yeah, I figured.

>         Pointer arithmetics is required to read the next block at the
> right offset in the buffer. When the whole input buffer has been read,
> read() will return 0.
>         At least that's the assumption and rationale behind this. I
> don't have my UNPv1 handy to crosscheck.

I know, and it looks OK.
> > Does the debug call show up in the logs? If so, what does it log?
>         If ti does, no-one's told me about it.
> Alex

Right. Maybe an external call is crashing on a call hidden in it?

-------------- next part --------------
Wifidog mailing list
Wifidog at isf.waglo.com

More information about the Wifidog mailing list