MobileRead Forums - View Single Post

Krystian Galaj · 05-12-2010, 07:14 AM

It looks to me like either a buffer overflow, or the filename string that's not properly ending with NULL.

I understand that the error is what was written out, and the "You need GLIBC..." string was considered the part of the path by some function, and that caused the "file name too long" error. So either the '/tmp/images/Note\r' isn't properly zero-terminated (more probable), or "You need GLIBC..." string was copied in memory over the latter part of the path (less probable).

05-12-2010, 07:14 AM	#4
Krystian Galaj Guru Posts: 820 Karma: 11012 Join Date: Nov 2007 Location: Warsaw, Poland Device: Bookeen Cybook	It looks to me like either a buffer overflow, or the filename string that's not properly ending with NULL. I understand that the error is what was written out, and the "You need GLIBC..." string was considered the part of the path by some function, and that caused the "file name too long" error. So either the '/tmp/images/Note\r' isn't properly zero-terminated (more probable), or "You need GLIBC..." string was copied in memory over the latter part of the path (less probable).