GNU bug report logs - #76559
31.0.50; [-O3 + PGTK] Crash when 'copying as kill'/'killing word'

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Iurie Marian <marian.iurie <at> gmail.com>, Po Lu <luangruo <at> yahoo.com>
Cc: michael.albinus <at> gmx.de, iura.mail <at> gmail.com, 76559 <at> debbugs.gnu.org
Subject: bug#76559: 31.0.50; [-O3 + PGTK] Crash when 'copying as kill'/'killing word'
Date: Wed, 26 Feb 2025 18:35:37 +0200

> From: Iurie Marian <marian.iurie <at> gmail.com>
> Date: Wed, 26 Feb 2025 17:03:29 +0100
> Cc: Iurie Marian <iura.mail <at> gmail.com>, 76559 <at> debbugs.gnu.org, michael.albinus <at> gmx.de
> 
> `dpyinfo` is actually invalid...
> 
> (gdb) p *event
> $3 = {kind = SELECTION_REQUEST_EVENT, dpyinfo = 0x55c83670, requestor
> = 0x555556035a80, selection = 0x45, target = 0x4d, property = 0x60,
> time = 0}
> 
> (gdb) p *event->dpyinfo
> Cannot access memory at address 0x55c83670
> 
> (gdb) x/s 0x55c83670
> 0x55c83670:     <error: Cannot access memory at address 0x55c83670>
> 
> (gdb) p event->dpyinfo->terminal
> Cannot access memory at address 0x55c83678

So dpyinfo got freed somehow?

 Po Lu, any suggestions or ideas?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.