I was looking at the code for strstr(s1, s2) and I do not understand how
it does what it's supposed to do. The only exit points return NULL or
the original pointer to s1. How does strstr() return the pointer to the
substring it's supposed to be looking for?
Jody, All,
On 2015-01-04 10:04 -0500, Jody Bruchon spake thusly:
I was looking at the code for strstr(s1, s2) and I do not understand how it
does what it's supposed to do. The only exit points return NULL or the
original pointer to s1. How does strstr() return the pointer to the
substring
On Sat, Dec 27, 2014 at 03:51:46PM -0500, Anthony G. Basile wrote:
Hi everyone,
I hit a bug in all versions of uclibc when building for TARGET=arm
using gcc-4.8.3 with -fstack-check. This is a new option introduced
in gcc-4.8 which checks that you don't go past the boundary of the
stack in
From c42bb573e9a2deb841181082efd3313d89494cf9 Mon Sep 17 00:00:00 2001
From: Jody Bruchon j...@c02ware.com
Date: Sun, 4 Jan 2015 13:45:11 -0500
Subject: [PATCH] Replace strstr() implementations with faster two-way version
Two strstr() implementations exist within uClibc: a naive one
used when
Whoops, it seems I typed Stephen's initials wrong in that patch text.
s/SJVDB/SRVDB/g and apologies for that.
___
uClibc mailing list
uClibc@uclibc.org
http://lists.busybox.net/mailman/listinfo/uclibc
