Re:Found a nice bug in IOS today, bricks your phone and kill...
by gedekran on Thursday April 28, 2011 @06:56AM
(#2492855)
More apt would have been that it disables your iphone temporarily until a factory reset or restore is performed. Saying it bricks it causes me to think back to messing up the flashing of firmware on a device and the device never working again.
Re:Found a nice bug in IOS today, bricks your phone and kill...
by Fjanth on Thursday April 28, 2011 @07:14AM
(#2492890)
Yeah, I know. Its to bad though because all the discussions are turning into discussions about the proper use of "bricking".
Re:Found a nice bug in IOS today, bricks your phone and kill...
by sirclueless on Thursday April 28, 2011 @07:34AM
(#2492926)
Well, I'm pretty sure that getting "fscked" is not that bad. I mean, running file-system checks is probably a good idea to do periodically.
Re:Found a nice bug in IOS today, bricks your phone and kill...
by demallien on Thursday April 28, 2011 @07:56AM
(#2492975)
Wait. Is it really an endless loop, or just a queue that is getting filled up faster than it empties resulting in a more DOS-style problem? Because it sounds much more like the second case, in which case not only does it not brick the phone, but it isn't even a bug...
Re:Found a nice bug in IOS today, bricks your phone and kill...
by Fjanth on Thursday April 28, 2011 @08:19AM
(#2493021)
OP:Nope, you didnt read the code. Try reading the other version I posted. Works without a loop as well.
Re:Found a nice bug in IOS today, bricks your phone and kill...
by demallien on Thursday April 28, 2011 @08:37AM
(#2493059)
errr, that's what I said...
Re:Found a nice bug in IOS today, bricks your phone and kill...
by Fjanth on Thursday April 28, 2011 @09:20AM
(#2493176)
Which is why I wrote "OP" in front :)
Re:Found a nice bug in IOS today, bricks your phone and kill...
by demallien on Thursday April 28, 2011 @10:32AM
(#2493446)
In the post that I replied to, you said that Springboard is getting into an endless loop. Having looked at the code that you posted, I commented that it doesn't look like an endless loop but more like a denial of service type problem, to which you replied that I should read the code, and that it doesn't need a loop, which was just repeating my point about it not appearing to be a loop!
Ahhh, I give up. Just try reading what I wrote before replying, mkay?
Re:Found a nice bug in IOS today, bricks your phone and kill...
by gpambrozio on Thursday April 28, 2011 @08:34AM
(#2493050)
If you try hard enough you can always find a piece (or many) of code that will "brick" (using your definition...) your device (whatever that is). I don't consider this a bug, or not a serious one at least.
And in this case Apple's approval process could protect the consumer. They would never let something like this past the gates.
Re:Found a nice bug in IOS today, bricks your phone and kill...
by DrJokepu on Thursday April 28, 2011 @09:50AM
(#2493274)
If a sandboxed application can get the sandboxing environment into a state where the only way to get the sandboxing environment working again is by restoring it from a backup, that is a serious defect in that environment.
Also, since this issue is very trivial to trigger, it's not very difficult to hide the triggering mechanism in a malicious application in a way that even a reasonably thorough source code inspection would not necessarily spot it. See also: The Underhanded C Contest.
The problem seems to be that springboard locks up in an endless loop, restarting the device wont help it because its still loading the offending notification from the cache.