~dr|z3d
@RN
@T3s|4_
@eyedeekay
@orignal
@postman
@zzz
%Liorar
%acetone
%cumlord
%snex
+FreefallHeavens_
+Xeha
+ardu
+hk
+mareki2p
+onon_
+r00tobo
+radakayot
+uop23ip
AHON1
Arch
Danny
DeltaOreo
Irc2PGuest28644
Irc2PGuest4450
Irc2PGuest70966
Irc2PGuest87589
Meow
Onn4l7h
Onn4|7h
SigSegv
altonen
maylay
not_bob_afk
plap
poriori_
profetik1
qend-irc2p
shiver_
simprelay
solidx66
thetia
u5657
usr001
weko_
woodwose
zer0bitz
dr|z3d
does this look saner, or am I making the same mistake here?
dr|z3d
b32 = reader.readLine();
dr|z3d
if (b32 == null) {return;}
zzz
same
dr|z3d
yeah, figured.
dr|z3d
so, totally pointless then, as you say. this should cover it: while((b32 = reader.readLine()) != null) {
dr|z3d
well, not totally pointless, as it prevents the issue from triggering, but not the correct fix.
dr|z3d
what about checking the filesize instead?
dr|z3d
int fileLength = (int) file.length();
dr|z3d
if (fileLength == 0) {return;}
zzz
better
zzz
but the reason for a ticket was that this is low priority, not for today, so if you want my analysis you'll have to sit tight ))
dr|z3d
sure, I don't think it's something that'll affect most people.
dr|z3d
if there's no file at all, non-issue. only zero length file, or presumably a file containing no b32s.
dr|z3d
got a stacktrace zzz, bug report updated.