Bug 13354

Summary:

Xcms.txt causes memory corruption

Product:

xorg

Reporter:

walter <wharms>

Component:

Lib/Xt

Assignee:

Xorg Project Team <xorg-team>

Status:

RESOLVED FIXED

QA Contact:

Xorg Project Team <xorg-team>

Severity:

normal

Priority:

medium

CC:

jesserayadkins, matthieu.herrb

Version:

7.2 (2007.02)

Hardware:

x86 (IA32)

OS:

All

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
Xcms that causes crash	none

Description walter 2007-11-22 07:14:25 UTC

I was trying to define colors in Xcms.txt (to replace my rgb.txt).
when i was trying the new color(s). When XrmQGetSearchResource()  caused a crash.


here is the xterm output:

(gdb) r -bg IMIS1
Starting program: /usr/bin/xterm -bg IMIS1
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
*** glibc detected *** /usr/bin/xterm: malloc(): memory corruption: 0x080b4a70 ***
(no debugging symbols found)
======= Backtrace: =========
/lib/libc.so.6[0xb7b684b6]
/lib/libc.so.6[0xb7b6a701]
/lib/libc.so.6(__libc_malloc+0x97)[0xb7b6bd07]
/usr/lib/libxcb.so.1[0xb7acd745]
/usr/lib/libxcb.so.1[0xb7acc2dd]
/usr/lib/libxcb.so.1(xcb_wait_for_reply+0x126)[0xb7acde66]
/usr/lib/libX11.so.6(_XReply+0x12b)[0xb7da8afb]
/usr/lib/libX11.so.6(XAllocNamedColor+0xe5)[0xb7d84e45]
/usr/lib/libXt.so.6(XtCvtStringToPixel+0x1de)[0xb7ca481e]
/usr/lib/libXt.so.6[0xb7c9f558]
/usr/lib/libXt.so.6(_XtConvert+0xf0)[0xb7c9f8e0]
/usr/lib/libXt.so.6[0xb7cbc580]
/usr/lib/libXt.so.6(_XtGetResources+0x114)[0xb7cbd6e4]
/usr/lib/libXt.so.6[0xb7ca5e87]
/usr/lib/libXt.so.6(_XtAppCreateShell+0x85)[0xb7ca62e5]
/usr/lib/libXt.so.6(XtAppCreateShell+0xdc)[0xb7ca651c]
/usr/lib/libXt.so.6(XtOpenApplication+0xfa)[0xb7cb190a]
/usr/bin/xterm[0x80681c2]
/lib/libc.so.6(__libc_start_main+0xe0)[0xb7b17fe0]
/usr/bin/xterm[0x804d441]

<memorymap removed>

btw; using xterm without -bg causes:
xterm
*** glibc detected *** xterm: corrupted double-linked list: 0x080af5e8 ***
======= Backtrace: =========
/lib/libc.so.6[0xb7b484b6]
/lib/libc.so.6[0xb7b49e4a]
/lib/libc.so.6(cfree+0x89)[0xb7b4a179]
/lib/libc.so.6(fclose+0x135)[0xb7b38c35]
/usr/lib/libX11.so.6[0xb7dcd00d]
/usr/lib/libX11.so.6[0xb7dcd2e5]
/usr/lib/libX11.so.6(_XcmsResolveColorString+0xde)[0xb7dcd3ee]
/usr/lib/libX11.so.6(XAllocNamedColor+0x50)[0xb7d64db0]
/usr/lib/libXt.so.6(XtCvtStringToPixel+0x1de)[0xb7c8481e]
/usr/lib/libXt.so.6[0xb7c7f558]
/usr/lib/libXt.so.6(_XtConvert+0xf0)[0xb7c7f8e0]
/usr/lib/libXt.so.6[0xb7c9c580]
/usr/lib/libXt.so.6(_XtGetResources+0x114)[0xb7c9d6e4]
/usr/lib/libXt.so.6[0xb7c85e87]
/usr/lib/libXt.so.6(_XtAppCreateShell+0x85)[0xb7c862e5]
/usr/lib/libXt.so.6(XtAppCreateShell+0xdc)[0xb7c8651c]
/usr/lib/libXt.so.6(XtOpenApplication+0xfa)[0xb7c9190a]
xterm[0x80681c2]
/lib/libc.so.6(__libc_start_main+0xe0)[0xb7af7fe0]
xterm[0x804d441]

Comment 1 walter 2007-11-22 07:16:49 UTC

Created attachment 12689 [details]
Xcms that causes crash

This Xcms.txt causes errors and it may contain even more errors

Comment 2 walter 2008-04-04 09:02:36 UTC

the problem is caused by a broken Xcms parsing code 
see also Bug 15305

Comment 3 Jesse Adkins 2010-12-01 19:49:20 UTC

Is this still an issue with a newer version of xserver?

Comment 4 walter 2010-12-02 10:02:30 UTC

i have posted a fix some time ago and so far i know the problem is "fixed".
NTL a better parser is requiered

Comment 5 Jeremy Huddleston Sequoia 2011-10-07 17:42:32 UTC

Reported fixed, closing.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.