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

Re: Possible NPTL bugs?



On Sun, 2003-01-12 at 00:07, Warren Togami wrote:
> When running the following kernels and glibc's the two problems 
> described below occur.
> kernel-2.4.20-2.2
> kernel-2.4.20-2.11
> glibc-2.3.1-21
> glibc-2.3.1-32
> 
> When running this kernel from Psyche the below problems do not occur:
> kernel-2.4.18-19.8.0
> 
> 
> Problem #1
> ===========
> XMMS seems to crash with the following message when you have a file in 
> the playlist that no longer exists on the filesystem.
> 
> read(3, "\1\1O\f\0\0\0\0h\0 \2\0\0\0\0\0\0\0\0\0\0\0\0\300\210\270"..., 
> 32) = 32brk(0)                                  = 0x8212000
> brk(0x8213000)                          = 0x8213000
> mmap2(NULL, 8388608, PROT_READ|PROT_WRITE|PROT_EXEC, 
> MAP_PRIVATE|MAP_ANONYMOUS,
> -1, 0) = 0x4212a000
> mprotect(0x4212a000, 4096, PROT_NONE)   = 0
> clone(child_stack=0x42929930, 
> flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|0x790000) = 3006
> write(3, ">\0\7\0\360\0 \2f\0 \2s\0 \2\27\0\0\0\'\0X\0\27\0\22\0"..., 
> 48) = 48
> read(3, 0xbffff280, 32)                 = -1 EAGAIN (Resource 
> temporarily unavailable)
> select(4, [3], NULL, NULL, NULL)        = 1 (in [3])
> read(3, "\1\1R\f\0\0\0\0h\0 \2\0\0\0\0\0\0\0\0\0\0\0\0\300\210\270"..., 
> 32) = 32futex(0x42929fb8, FUTEX_WAIT, 3006, NULL
> Segmentation fault
> 
> You've probably found a bug in XMMS, please visit
> http://bugs.xmms.org and fill out a bug report.
> 
> ) = 0
> 

Seen this with xmms, reported it to xmms directly. They said they
couldn't reproduce it on their machines. Ended up suspecting it was a
redhat issue. Haven't gotten around to submitting it to RedHat. Feel
free to open a bug report with RedHat, and mention my xmms bug report.

http://bugs.xmms.org/show_bug.cgi?id=1160





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