[DGD] dgd, comm.c: 850: Why is this a fatal error?

Raymond Jennings shentino at gmail.com
Tue Nov 12 14:39:21 CET 2013


Well...I managed to get a core dump just yesterday whose backtrace fingered
this line.

I was using intermudd on kotaka and was having some network trouble at the
time.

I also believe a hotboot was involved.

Does this mean I stumbled on a bug?


On Tue, Nov 12, 2013 at 1:19 AM, Felix A. Croes <felix at dworkin.nl> wrote:

> Raymond Jennings <shentino at gmail.com> wrote:
>
> > I'm just curious, why is this a fatal error?  Looking at the docs it
> would
> > seem that a failure to connect would rather result in a close() or an
> > unconnected() call.
>
> When you read the code of conn_connect(), you'll see that the function
> does not return NULL when it cannot establish a connection, but rather
> when there is an internal consistency problem in DGD or it cannot use
> operating system calls as expected.  An actual failure to establish a
> connection should not occur in this function because the socket is
> non-blocking.
>
> Regards,
> Felix Croes
> ____________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd
>



More information about the DGD mailing list