From 2f07f71d787dc2dfcefac6a1f723c2cde76d4884 Mon Sep 17 00:00:00 2001 From: Martin Pool Date: Tue, 18 Mar 2003 05:31:52 +0000 Subject: The new string macros catch a bug at compile that previously only trapped at runtime, which is great. So we have to try a little harder to provoke an overflow -- which is still caught nicely in developer mode. (This used to be commit cea126f62ad411f5efbebc7c5d39297fd8ef9efb) --- source3/torture/t_stringoverflow.c | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'source3/torture') diff --git a/source3/torture/t_stringoverflow.c b/source3/torture/t_stringoverflow.c index b0503adb8f..ec14d81189 100644 --- a/source3/torture/t_stringoverflow.c +++ b/source3/torture/t_stringoverflow.c @@ -3,6 +3,7 @@ int main(void) { fstring dest; + char *ptr = dest; printf("running on valgrind? %d\n", RUNNING_ON_VALGRIND); @@ -10,7 +11,13 @@ * will actually fit, but this is still wrong because you * can't pstrcpy into an fstring. This should trap in a * developer build. */ + +#if 0 + /* As of CVS 20030318, this will be trapped at compile time! */ pstrcpy(dest, "hello"); +#endif /* 0 */ + + pstrcpy(ptr, "hello!"); return 0; } -- cgit