[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] First Byte of Body Lost on inc(1).
From: |
David Levine |
Subject: |
Re: [Nmh-workers] First Byte of Body Lost on inc(1). |
Date: |
Mon, 05 Sep 2016 23:09:56 -0400 |
Ken wrote:
> > [Ralph wrote:]
> > 1 memmove(0x13e61a0, "\n\nab\n", 5) = 0x13e61a0
>
> That looks like it happens in sbr/m_getfld.c:read_more().
I think that first character is missed here:
> > 2 memcpy(0x13ec980, "b\n", 2) = 0x13ec980
That's this line (738) in m_getfld():
memcpy( buf, bp, c );
with bp off by one, I think due to this increment in Getc():
if (read_more (s) == 0) {
/* Pretend that we read a character. That's what stdio does. */
++s->readpos;
return EOF;
}
In spite of the comment, I don't know why readpos needs to be incremented.
Also, I noticed:
<address@hidden>
David
- [Nmh-workers] First Byte of Body Lost on inc(1)., Ralph Corderoy, 2016/09/05
- Re: [Nmh-workers] First Byte of Body Lost on inc(1)., Ken Hornstein, 2016/09/05
- Re: [Nmh-workers] First Byte of Body Lost on inc(1)., Ralph Corderoy, 2016/09/05
- Re: [Nmh-workers] First Byte of Body Lost on inc(1)., Ken Hornstein, 2016/09/05
- Re: [Nmh-workers] First Byte of Body Lost on inc(1)., Ralph Corderoy, 2016/09/05
- Re: [Nmh-workers] First Byte of Body Lost on inc(1)., Ken Hornstein, 2016/09/05
- Re: [Nmh-workers] First Byte of Body Lost on inc(1)., Ralph Corderoy, 2016/09/05
- Message not available
- Re: [Nmh-workers] First Byte of Body Lost on inc(1)., Ken Hornstein, 2016/09/05
- Re: [Nmh-workers] First Byte of Body Lost on inc(1).,
David Levine <=
- Re: [Nmh-workers] First Byte of Body Lost on inc(1)., David Levine, 2016/09/06