From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-21647-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 6298 invoked by alias); 24 May 2005 14:09:28 -0000
Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb/>
List-Post: <mailto:gdb@sources.redhat.com>
List-Help: <mailto:gdb-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-owner@sources.redhat.com
Received: (qmail 5886 invoked by uid 22791); 24 May 2005 14:09:11 -0000
Received: from host217-40-213-68.in-addr.btopenworld.com (HELO SERRANO.CAM.ARTIMI.COM) (217.40.213.68)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 24 May 2005 14:09:11 +0000
Received: from mace ([192.168.1.25]) by SERRANO.CAM.ARTIMI.COM with Microsoft SMTPSVC(6.0.3790.211);
	 Tue, 24 May 2005 15:09:10 +0100
From: "Dave Korn" <dave.korn@artimi.com>
To: =?iso-8859-1?Q?'Ion_Gazta=F1aga'?= <ion_g_m@terra.es>,
	"'Daniel Jacobowitz'" <drow@false.org>
Cc: <gdb@sources.redhat.com>,
	<kewarken@qnx.com>
Subject: RE: Error building qnx cross-gdb 6.3
Date: Tue, 24 May 2005 14:09:00 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <000b01c5601d$2ff04240$0a001aac@amd1ghzwinxp>
Message-ID: <SERRANOaH5qRFapNuT100000104@SERRANO.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 24 May 2005 14:09:10.0292 (UTC) FILETIME=[27F25540:01C5606A]
X-SW-Source: 2005-05/txt/msg00302.txt.bz2

----Original Message----
>From: Ion Gazta=F1aga
>Sent: 24 May 2005 05:58


> The created i386-pc-nto-qnx6.3.0-gdb.exe.stackdump was:
>=20
> Exception: STATUS_ACCESS_VIOLATION at eip=3D0042012D
> eax=3D00000039 ebx=3D00000039 ecx=3D00000000 edx=3D00000039 esi=3D61782CD8
> edi=3D00000001
> ebp=3D0022ECE8 esp=3D0022ECE4
>
program=3DC:\cygwin\tools\i386-pc-nto-qnx6.3.0\bin\i386-pc-nto-qnx6.3.0-gdb=
.ex
e,
> pid 920, thread main
> cs=3D001B ds=3D0023 es=3D0023 fs=3D003B gs=3D0000 ss=3D0023
> Stack trace:
> Frame     Function  Args
> 0022ECE8  0042012D  (00000039, 00000000, 0062A650, 005E122C)
> 0022ED28  004E0F60  (61782CD8, 00000000, 0022ED48, 00403DB6)
> 0022ED38  00425F89  (006283B0, 00000400, 0022EE98, 00401616)
> 0022ED48  00403DB6  (61782D00, 61782CD8, 0058E0E2, 00583000)
> 0022EE98  00401616  (0022F050, 0022F060, 0022EFD8, 004020F5)
> 0022EEA8  00402281  (005834D0, 0022F010, 0022EFB4, 00000000)
> 0022EFD8  004020F5  (00402270, 005834D0, 0022F010, 0022F008)
> 0022F018  004022E0  (00401110, 0022F050, 0058E0E2, 00000006)
> 0022F038  00401DF3  (0022F050, 00000754, 0022F068, 6109106A)
> 0022F068  004010AA  (00000001, 61782CD8, 101000A8, 0022F0C0)
> 0022F0A8  61005F34  (0022F0C0, 7C920833, 77D197E4, 77D19812)
> 0022FF88  6100614B  (00000000, 00000000, 00000000, 00000000)
> End of stack trace


  Why don't you debug it with native gdb?  You could also get a more
meaningful backtrace by running

addr2line --exe=3D/tools/i386-pc-nto-qnx6.3.0/bin/i386-pc-nto-qnx6.3.0-gdb.=
exe

and cutting and pasting the column of addresses under 'Function' into it.



    cheers,
      DaveK
--=20
Can't think of a witty .sigline today....