On Sun, 3 Jun 2001 18:29:52 -0400 (EDT), Daniel Eischen wrote:
> On Mon, 4 Jun 2001, Bruce Evans wrote:
> > On Sat, 2 Jun 2001, Maxim Sobolev wrote:
> >
> > > It seems that something is wrong with sscanf(3) in -current - in
> > > some cases it may cause SIGBUS. I failed to reproduce the
> > > pro
On Mon, 4 Jun 2001, Bruce Evans wrote:
> On Sat, 2 Jun 2001, Maxim Sobolev wrote:
>
> > It seems that something is wrong with sscanf(3) in -current - in
> > some cases it may cause SIGBUS. I failed to reproduce the
> > problem on 4-STABLE, so it is a -current specific bug. Attached
> > please fin
On Sat, 2 Jun 2001, Maxim Sobolev wrote:
> It seems that something is wrong with sscanf(3) in -current - in
> some cases it may cause SIGBUS. I failed to reproduce the
> problem on 4-STABLE, so it is a -current specific bug. Attached
> please find small showcase that exposes the bug in question
>
Hi,
It seems that something is wrong with sscanf(3) in -current - in
some cases it may cause SIGBUS. I failed to reproduce the
problem on 4-STABLE, so it is a -current specific bug. Attached
please find small showcase that exposes the bug in question
and a backtrace after SIGBUS.
Please fix.
-M
