Summary: | media-tv/xawtv-3.95-r1: fbtv fails with "mmap: Cannot allocate memory" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stefan Bauer <stefan.andreas.bauer> |
Component: | Current packages | Assignee: | Television related Applications in Gentoo's Portage <media-tv> |
Status: | RESOLVED CANTFIX | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
strace for emerged xawtv/fbtv
strace for self compiled xawtv/fbtv |
Description
Stefan Bauer
2008-03-18 08:56:32 UTC
Created attachment 146459 [details]
strace for emerged xawtv/fbtv
See line 200: 3,2 GB should be mapped. This fails gently.
Created attachment 146460 [details]
strace for self compiled xawtv/fbtv
See line 107: 4 MB (correct size) should be mapped. Thereafter something went wrong, the console freezes. You can still work blind.
The main difference to emerged fbtv is that no plugins could be loaded. So maybe a xawtv plugin caused the wrong size detection.
Several gdb sessions of the self-compiled fbtv also freezed. Location: fbtools.c, function fb_setvt, line 268, "switch(fork()) {" The above listed hardware works with Debian Etch, so there's no hardware issue. Gentoo fails even on an BX-board with a G450 (matroxfb). Further debugging brought up, that the mmap error is caused at fbtools.c:428. fb_mem_offset is a huge negative value at this point. In my self compiled fbtv, this value was 0. The console freezes later in fb_activate_current. Closing this, because the machine where this has happened doesn't exist anymore. |