On 05/09/2012 01:07 PM, Christophe Fergeau wrote:
Hey,
On Mon, May 07, 2012 at 04:30:22PM +0300, Uri Lublin wrote:
On 05/03/2012 07:09 PM, Christophe Fergeau wrote:
On Thu, May 03, 2012 at 06:04:39PM +0300, Uri Lublin wrote:
From: Arnon Gilboa
no strtok_r (reentrent) available, so use strtok
Hey,
On Mon, May 07, 2012 at 04:30:22PM +0300, Uri Lublin wrote:
> On 05/03/2012 07:09 PM, Christophe Fergeau wrote:
> >On Thu, May 03, 2012 at 06:04:39PM +0300, Uri Lublin wrote:
> >>From: Arnon Gilboa
> >>
> >>no strtok_r (reentrent) available, so use strtok instead.
> >Wouldn't it be safer to u
On 05/03/2012 07:09 PM, Christophe Fergeau wrote:
On Thu, May 03, 2012 at 06:04:39PM +0300, Uri Lublin wrote:
From: Arnon Gilboa
no strtok_r (reentrent) available, so use strtok instead.
Wouldn't it be safer to use strtok_s? Any application using threads and
strtok and libusbredirparser could
Hi,
On 05/03/2012 06:09 PM, Christophe Fergeau wrote:
On Thu, May 03, 2012 at 06:04:39PM +0300, Uri Lublin wrote:
From: Arnon Gilboa
no strtok_r (reentrent) available, so use strtok instead.
Wouldn't it be safer to use strtok_s? Any application using threads and
strtok and libusbredirparser
On Thu, May 03, 2012 at 06:04:39PM +0300, Uri Lublin wrote:
> From: Arnon Gilboa
>
> no strtok_r (reentrent) available, so use strtok instead.
Wouldn't it be safer to use strtok_s? Any application using threads and
strtok and libusbredirparser could get issues with this change no?
>
> Modified
From: Arnon Gilboa
no strtok_r (reentrent) available, so use strtok instead.
Modified-by: Uri Lublin
---
usbredirparser/usbredirfilter.c | 16 +++-
1 files changed, 11 insertions(+), 5 deletions(-)
diff --git a/usbredirparser/usbredirfilter.c b/usbredirparser/usbredirfilter.c
in
