Re: CPPCheck found 24 high risk bugs in Git v.1.8.3.4

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: CPPCheck found 24 high risk bugs in Git v.1.8.3.4

From: Andreas Schwab <hidden>
Date: 2016-06-15 22:58:28

Erik Faye-Lund [off-list ref] writes:
I don't see how it's undefined. It's using the memory that 'pos'
*points to* that is undefined, no? The difference between 'pos' and
'str' should still be the same, it's not like realloc somehow
magically updates 'pos'...
It does.  Think of segmented architectures, where freeing a pointer
invalidates its segment, so that even loading the value of the pointer
traps.  Probably no such architecture is in use any more, though.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: CPPCheck found 24 high risk bugs in Git v.1.8.3.4

From: Erik Faye-Lund <hidden>
Date: 2016-06-15 22:58:28

On Wed, Aug 21, 2013 at 1:01 AM, Andreas Schwab [off-list ref] wrote:
Erik Faye-Lund [off-list ref] writes:
quoted
I don't see how it's undefined. It's using the memory that 'pos'
*points to* that is undefined, no? The difference between 'pos' and
'str' should still be the same, it's not like realloc somehow
magically updates 'pos'...
It does.  Think of segmented architectures, where freeing a pointer
invalidates its segment, so that even loading the value of the pointer
traps.  Probably no such architecture is in use any more, though.
Wow, you're right. And since doing it the right way is pretty much the same
complexity (and possibly even a bit easier to follow), that's probably the
best thing to go with, then. Thanks for keeping me straight!
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help