From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-21779-listarch-gdb=sources.redhat.com@sources.redhat.com>
Received: (qmail 27731 invoked by alias); 7 Jun 2005 16:10:18 -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 27687 invoked by uid 22791); 7 Jun 2005 16:10:10 -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, 07 Jun 2005 16:10:10 +0000
Received: from mace ([192.168.1.25]) by SERRANO.CAM.ARTIMI.COM with Microsoft SMTPSVC(6.0.3790.211);
	 Tue, 7 Jun 2005 17:10:02 +0100
From: "Dave Korn" <dave.korn@artimi.com>
To: "'Renzhong Xiao'" <rzxiao@gmail.com>,
	<gdb@sources.redhat.com>
Subject: RE: How GDB handle this case while program works well in GDB but crash in mormal mode
Date: Tue, 07 Jun 2005 16:10:00 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <2be97658050605075650ee2704@mail.gmail.com>
Message-ID: <SERRANOa0xtAEHLB8Tr00000310@SERRANO.CAM.ARTIMI.COM>
X-SW-Source: 2005-06/txt/msg00062.txt.bz2

----Original Message----
>From: Renzhong Xiao
>Sent: 05 June 2005 15:57

> Hi,
>     I have some trouble in using GDB 6.3.50_2004-12-28-cvs in Cygwin
> to debug the mencoder (which is a program in MPlayer).When I run
> mencoder in normal mode,it will pop up an error message saying
> mencoder.exe has error and will be closed. But I run mencoder in
> gdb,it works well.
>     I don't know how to find this bug in GDB,Does GDB has the some
> feature to handle this case?
> 
>     Any information will be very appreciate!
> 
> Renzhong Xiao


  Perhaps you can use the cygwin just-in-time debugging ability to solve the
problem; that way the program will run as usual, without the debugger
attached, up to the point when the error occurs; then cygwin will attach the
debugger once the error has happened.  Hopefully that means the initial
stages of running the program will be undisturbed and the error will not be
masked.

  To make this work, add 'error_start=C:\cygwin\bin\gdb.exe' (or whatever
else is the win32 path to gdb.exe, according to where you installed cygwin)
to your $CYGWIN environment variable before you start a cygwin shell, then
run mencoder.  Hopefully as soon as it crashes cygwin will attach teh
debugger for you.


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