Bug 11389

Summary: [x86_64]UMark cause Segmantation Fault on 64bit platform
Product: DRI Reporter: he jiang <jiang.he>
Component: GeneralAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED NOTOURBUG QA Contact:
Severity: normal    
Priority: medium CC: gordon.jin, haihao.xiang, wei.z.wang
Version: DRI git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description he jiang 2007-06-26 19:34:34 UTC
UMark is Benchmark tool for ut2004. It's an important tool to test ut2004's performance.
It can be downloaded from http://ut2k3botbench.sourceforge.net/index.php

System Enviroment:
--------------------------

--Platform : 915/945/965/G33
--Architecture(ia32,ia32e,compatiblity):ia32e(x86_64)
--OS:FC6

Bug detailed description:
--------------------------
Run UMark(Benchmark tool for ut2004) will cause Segmentation Fault while running ut2004 is normal.


Reproduce steps:
----------------
1.startup X
2.run umark


Current result:
----------------
Segmentation Fault
Comment 1 he jiang 2007-06-26 21:20:09 UTC
backtrace log : 
------------------------------------------------------
(gdb) r
Starting program: /usr/local/bin/umark
[Thread debugging using libthread_db enabled]
[New Thread 47493248724224 (LWP 16234)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47493248724224 (LWP 16234)]
0x0000003ab58754f0 in strlen () from /lib64/libc.so.6
(gdb) bt
#0  0x0000003ab58754f0 in strlen () from /lib64/libc.so.6
#1  0x0000003ab5845cb8 in vfprintf () from /lib64/libc.so.6
#2  0x0000003ab586652d in vasprintf () from /lib64/libc.so.6
#3  0x0000003ab7053bc0 in g_vasprintf () from /lib64/libglib-2.0.so.0
#4  0x0000003ab70463b0 in g_strdup_vprintf () from /lib64/libglib-2.0.so.0
#5  0x0000003ab704644d in g_strdup_printf () from /lib64/libglib-2.0.so.0
#6  0x0000000000403e6f in main (argc=1, argv=0x7fffc94b5d68) at main.c:122
(gdb)
Comment 2 Michel Dänzer 2007-06-26 23:42:53 UTC
I only see umark, glib and libc in the backtrace.

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.