[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#384854: marked as done (SIGSEGV in sendfile64())

Your message dated Sun, 27 Aug 2006 15:18:19 +0200
with message-id <44F19B9B.6060308@aurel32.net>
and subject line Bug#384854: SIGSEGV in sendfile64()
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: libc6
Version: 2.3.6.ds1-4

Using the
int stat (const char *filename, struct stat *buf)
function in a programm on a certain filename causes a segmentation fault.

For example:
[...]
struct stat *stats;
stat("/home/daniel/music/Singles/Spax, Flowin Immo, Toni L u.a", stats);
[...]

gdb Output:
[...]
Program received signal SIGSEGV, Segmentation fault.
0xb7f2c625 in sendfile64 () from /lib/tls/libc.so.6
[...]

Using stat64() instead, works well.
And if I rename the directory and remove the trailing 'a' or add another
one, it also works.

--- End Message ---
--- Begin Message --- 
Daniel Weindl a écrit :

Aurelien Jarno said the following on 08/27/06 14:14:

Daniel Weindl a écrit :

Package: libc6
Version: 2.3.6.ds1-4

Using the
int stat (const char *filename, struct stat *buf)
function in a programm on a certain filename causes a segmentation fault.

For example:
[...]
struct stat *stats;
stat("/home/daniel/music/Singles/Spax, Flowin Immo, Toni L u.a", stats);

Do you have a full testcase that could be compiled?

In the example you give, you are not allocating correctly the stats
buffer, I don't know if it is a simplification for the bug report or a
mistake in your code.



I just rechecked my code. I'm not sure why there wasn't always a
segfault, but it was an allocating problem as you said.
Sorry for bothering you. This report can be closed.



Closing it with this mail.


--
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

--- End Message ---
Reply to: