Bug 140224 – xmodmap crashes when reading default Xmodmap

Bug 140224 - xmodmap crashes when reading default Xmodmap

Summary:	xmodmap crashes when reading default Xmodmap

Status:	CLOSED DUPLICATE of bug 138458

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	xorg-x11 (Show other bugs)
Sub Component:
Version:	3
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	X/OpenGL Maintenance List
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-11-21 05:57 EST by Marcel Kyas
Modified:	2007-11-30 17:10 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-02-21 14:07:12 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Marcel Kyas 2004-11-21 05:57:30 EST

Description of problem:

xmodmap crashes with segmentation fault when reading /etc/X11/Xmodmap

Version-Release number of selected component (if applicable):

6.8.1

How reproducible:

xmodmap /etc/X11/Xmodmap

Steps to Reproduce:
1.
2.
3.
  
Actual results:

Segmentation violation

Expected results:

It terminates normally


Additional info:

I also filed the bug upstream at
https://bugs.freedesktop.org/show_bug.cgi?id=1875

Comment 1 Martin Blom 2004-11-22 11:21:13 EST

I'm not sure, but I don't think this happened before the upgrade to
xorg-x11-6.8.1-12.FC3.1.

Also the Layout Options in gnome-keyboard-properties seem to have no
effect anymore after upgrading. Could it be related or should I file a
new bug?

Comment 2 Marcel Kyas 2004-11-22 12:57:06 EST

Running xmodmap through valgrind gives me
==3561== 26 errors in context 1 of 1:
==3561== Invalid write of size 1
==3561==    at 0x1B902440: strcpy (mac_replace_strmem.c:199)
==3561==    by 0x8049675: (within /usr/X11R6/bin/xmodmap)
==3561==    by 0x804977F: (within /usr/X11R6/bin/xmodmap)
==3561==    by 0x8049155: (within /usr/X11R6/bin/xmodmap)
==3561==  Address 0x1B92A63B is 0 bytes after a block of size 19 alloc'd
==3561==    at 0x1B902A90: malloc (vg_replace_malloc.c:131)
==3561==    by 0x8048FD0: (within /usr/X11R6/bin/xmodmap)
==3561==    by 0x8049664: (within /usr/X11R6/bin/xmodmap)
==3561==    by 0x804977F: (within /usr/X11R6/bin/xmodmap)

I guess there is some off-by-one error in xmodmap.  Also, if I remove
all comments from the file, the crash is not triggered.  I hope this
helps to narrow it down.

Comment 3 Mike A. Harris 2004-11-22 15:53:32 EST


*** This bug has been marked as a duplicate of 138458 ***

Comment 4 Red Hat Bugzilla 2006-02-21 14:07:12 EST

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.