Andreas Schwab <schwab@xxxxxxxxxxxxxx> writes: > Erik Faye-Lund <kusmabite@xxxxxxxxx> 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. I love seeing that we have somebody who knows and can explain these dark corners of ANSI C standard ;-) -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html