[sane-devel] Intriquing Segfault Clues

[stef]

Le lundi 10 octobre 2011 19:11:23 Thomas H. George, vous avez écrit :
> The command xsane by user tom results in a segmentation fault.
> 
> The commands xsane -V and xsane -s by user tom run to completion.  The
> image file produced by xsane -s can be opened and edited by gimp.
> 
> If, when xsane -V has opened the xsane window, the choice
> Perferences/Setup is made the result is a segmentation fault.  I have
> not tried clicking on other options.
> 
> The bare command xsane run by root works perfectly.
> 
> The final lines produced by strace xsane /tmp/strace 2>&1 run by user tom
> are as follows
> 
> fcntl(12, F_SETFD, FD_CLOEXEC)          = 0
> fstat(12, {st_mode=S_IFREG|0644, st_size=49224, ...}) = 0
> mmap(NULL, 49224, PROT_READ, MAP_PRIVATE, 12, 0) = 0x7fd6ef61a000
> close(12)                               = 0
> poll([{fd=7, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=7,
> revents=POLLOUT}]) writev(7,
> [{"\214\3\n\0\260\0`\1%\0`\1\0\6@\0\0\0\0\0\0\0010\0\0\0\0\0 \2\0\0"...,
> 16380}, {NULL, 0}, {"", 0}], 3) = 16380 read(7, 0x24050c4, 4096)          
>      = -1 EAGAIN (Resource temporarily unavailable) brk(0x25dc000)        
>                  = 0x25dc000
> --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> +++ killed by SIGSEGV +++
> 
> where the file opened as 7 is passwd and the brk command is on line
> 28712 of the strace output.
> 
> I hope this information may pinpoint the cause of the segmentation fault
> because xsane run by gimp locks up just after the scanner completes the
> scan.
> 
> Tom

	Hello,

	have you considered to test xsane compiled with debug option (-ggdb and 
no -O2) through a debugger ? It should give you more information on the 
problem you have.

Regards,
	Stef