Fun fact: if you set pointers to 120 before passing them to free(), it doesn’t work at all This revelation brought to you by my last two days of debugging, at 5PM the day before vacation.
Prikaži ovu nit
(How does that even happen? Well, one of these types stores its capacity at the offset where the other one stores its buffer pointer 
)
-
-
Can you elaborate on this? In what situation would you access offsets instead of type-safe struct members? Thanks!
-
The code expected a CFString but got a bridged Swift String, and was accidentally missing a bridging check.
Kraj razgovora
Novi razgovor -
-
-
What if you fix that code just placing a valid pointer there (reorganizing the struct)? So the free() succeeds!
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.