Maybe this helps in tracing the bug:
(gdb) up 10
#10 0x0892a025 in fs_read_list_info (fpe=0x8bcf350, blockrec=0x8d65198)
at fserve.c:2376
2376in fserve.c
(gdb) p *pi
$1 = {num_offsets = 4, data_len = 134654824}
so it seems pi->data_len is fairly huge, maybe it is not initialized
earlier?
Branden Robinson wrote:
Hmm, well, given your backtrace, I might have been wrong about this being
SiS-specific.
#7 0x0848f646 in xf86SigHandler (signo=11) at xf86Events.c:1230
#8
#9 0x40142a1f in memcpy () from /lib/libc.so.6
Can you show us the output of "bt full -9" instead, plea
Branden Robinson wrote:
% gdb $(which XFree86-debug) core
If you could send us something smiliar, that would be very helpful.
OK, I got it. After another upgrade to `testing' today, and a reboot
for a kernel parameter earlier today, My SiS6326 card started to crash
more consistently, e
Branden Robinson wrote:
tag 284448 + moreinfo upstream
We're simply going to have to have accurate information before we can proceed.
[The following is a form letter.]
Can you reproduce the problem with xserver-xfree86-dbg? Install the
Situation is as follows:
- I can reproduce the bu
Branden Robinson wrote:
If the justification is "unknown", it might as well not be present.
Sorry, this is my first bug report (after using debian for many years,
since 0.7 or so), and I believe the script suggested that.
This bug is not a report of a Policy violation, nor does failure o
5 matches
Mail list logo