From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-34373-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 17654 invoked by alias); 11 May 2009 03:12:04 -0000
Received: (qmail 17644 invoked by uid 22791); 11 May 2009 03:12:03 -0000
X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 	tests=AWL,BAYES_00,RCVD_IN_JMF_BR,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout3.012.net.il (HELO mtaout3.012.net.il) (84.95.2.7)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 11 May 2009 03:11:57 +0000
Received: from conversion-daemon.i_mtaout3.012.net.il by i_mtaout3.012.net.il (HyperSendmail v2004.12) id <0KJG00800LWO2F00@i_mtaout3.012.net.il> for gdb@sourceware.org; Mon, 11 May 2009 06:11:54 +0300 (IDT)
Received: from HOME-C4E4A596F7 ([84.228.73.80]) by i_mtaout3.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0KJG009DOM7T3A21@i_mtaout3.012.net.il>; Mon, 11 May 2009 06:11:54 +0300 (IDT)
Date: Mon, 11 May 2009 03:12:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: how to debug this error by gdb?
In-reply-to: <6a8fced30905101934j2aa94d27i210484a99a523ce5@mail.gmail.com>
To: =?ISO-2022-JP?B?GyRCTEBrNBsoQg==?= <shi.minjue@gmail.com>
Cc: gdb@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <834ovsz62r.fsf@gnu.org>
References: <6a8fced30905101934j2aa94d27i210484a99a523ce5@mail.gmail.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2009-05/txt/msg00059.txt.bz2

> Date: Mon, 11 May 2009 10:34:52 +0800
> From: =?ISO-2022-JP?B?GyRCTEBrNBsoQg==?= <shi.minjue@gmail.com>
> 
> ---------------------------------------------------------------------------------------
> PUBLIC void glXWaitX(void)
> {
>   ......
>            if (psc->driScreen->waitX != NULL)
> [line 660]              (*psc->driScreen->waitX)(pdraw);
> .....
> }
> ---------------------------------------------------------------------------------------
> 
> 
> and here is the gdb info:
> ---------------------------------------------------------------------------------------
> (gdb) break glxcmds.c:660
> Breakpoint 1 (glxcmds.c:660) pending.
> (gdb) run
> Breakpoint 1, glXWaitX () at glxcmds.c:660
> (gdb) print psc->driScreen->waitX
> $3 = (void (*)(__GLXDRIdrawable *)) 0x47206769666e6f63
                                      ^^^^^^^^^^^^^^^^^^
This looks like ASCII text to me ("config G", little-endian).  So I'd
try to see if some code that runs before this place could overflow
some buffer with plain text, and part of that text spilled into this
pointer.

> (gdb) print *psc->driScreen->waitX
> Cannot access memory at address
> (gdb) step
> Program received signal SIGSEGV, Segmentation fault.

Right, because it's not NULL, but not a valid pointer, either.  Thus a
SIGSEGV.