Bug#618622: xserver-xorg-core: crash when resizing screen while running a fullscreen application
On Don, 2011-03-17 at 11:58 +0100, Michal Suchanek wrote:
> 2011/3/17 Michel Dänzer <daenzer@debian.org>:
> > On Don, 2011-03-17 at 11:44 +0100, Michal Suchanek wrote:
> >> 2011/3/17 Michel Dänzer <daenzer@debian.org>:
> >> > On Don, 2011-03-17 at 11:07 +0100, Michal Suchanek wrote:
> >> >>
> >> >> ==28521== Invalid write of size 1
> >> >> ==28521== at 0x4C26044: memcpy (mc_replace_strmem.c:497)
> >> >> ==28521== by 0x8FF277A: RADEONDownloadFromScreenCS (radeon_exa_funcs.c:667)
> >> >> ==28521== by 0x9693326: exaCopyDirty (exa_migration_classic.c:220)
> >> >> ==28521== by 0x9695D79: exaPrepareAccessReg_mixed (exa_migration_mixed.c:247)
> >> >> ==28521== by 0x969ED93: ExaCheckImageGlyphBlt (exa_unaccel.c:326)
> >> >> ==28521== by 0x56766D: miImageText8 (mipolytext.c:114)
> >> >> ==28521== by 0x4D07C6: damageImageText8 (damage.c:1547)
> >> >> ==28521== by 0x4399CC: doImageText (dixfonts.c:1559)
> >> >> ==28521== by 0x439A4F: ImageText (dixfonts.c:1604)
> >> >> ==28521== by 0x430342: ProcImageText8 (dispatch.c:2290)
> >> >> ==28521== by 0x4334D0: Dispatch (dispatch.c:431)
> >> >> ==28521== by 0x42575A: main (main.c:287)
> >> >> ==28521== Address 0xd4c0040 is 0 bytes after a block of size 5,242,880
> >> >
> >> > Can you run valgrind with --db-attach=yes and get a full gdb backtrace
> >> > at this point? (With xserver-xorg-core-dbg and
> >> > xserver-xorg-video-radeon-dbg installed)
> >>
> >> It does not offer to attach a debugger at this error.
> >
> > But it does at other errors?
> >
>
> No, running
>
> # valgrind --db-attach=yes Xorg :1
>
> just terminates after printing the m_mallocfree error.
Then obviously --db-attach=yes isn't taking effect... Is valgrind's
stdin/out connected to a terminal?
--
Earthling Michel Dänzer | http://www.vmware.com
Libre software enthusiast | Debian, X and DRI developer
Reply to: