Check resumeable file pointer with fstat.

[robinlinden]

This hopefully fixes a crash where uTox tries to fseek an invalid file pointer.

---

This change is 

[GrayHatter]

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

---

src/file_transfers.c, line 197 at r1 (raw file):

    }

    // This file pointer has a tendency of being both invalid and non-null so we use fstat to check it.

In this case it' getting bad data, which shouldn't be happening. Did you try to find the source of the bad data?

I'm okay with this pull either way, but this seems to be a bandaid, rather than sutures.

---

Comments from Reviewable

[robinlinden]

Review status: all files reviewed at latest revision, 1 unresolved discussion.

---

src/file_transfers.c, line 197 at r1 (raw file):

Previously, GrayHatter (Gregory Mullen) wrote…

In this case it' getting bad data, which shouldn't be happening. Did you try to find the source of the bad data?

I'm okay with this pull either way, but this seems to be a bandaid, rather than sutures.

Yeah, I tried to find the source before I resorted to this. I figured fixing the crash while still getting info about how often it is happening is good enough for now.

---

Comments from Reviewable

[GrayHatter]

---

Review status: all files reviewed at latest revision, all discussions resolved.

---

Comments from Reviewable

[e0ff]

---

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

---

Comments from Reviewable