X-Spam-Check-By: sourceware.org
Message-ID: <447A0F37.2080704@freenet.de>
Date: Sun, 28 May 2006 22:59:35 +0200
From: Ralf Habacker <ralf DOT habacker AT freenet DOT de>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: note about how-to-debug-cygwin.txt
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In the how-to-debug-cygwin.txt there is listed how to run application
using strace in gdb:

To debug this scenario, do something like this:

    bash$ gdb -nw yourapp.exe
    (gdb) dll cygwin1
    (gdb) l dll_crt0_1
    (gdb) b <<first line in the function>>
    (gdb) run
    (gdb) set strace.active=1
    (gdb) continue


According to winsup/cygwin/include/sys/strace.h the class member active
is known now as _active.

I have tried to get this running in gdb (cvs), but there is no output in
gdb. May be I have understand something wrong and the output is printed
somewhere else, but the sources tell me that strace uses
OutputDebugString(), which should be catched by gdb.
Or does gdb print it only when the application is currently running in
gdb and not in the gdb prompt ?

Regards
 Ralf

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEeg83oHh+5t8EXncRAnZtAJ0XI2URyUgm9n9nMxpjQWoXi5baJACdHFqP
eNp6sUbJ8SiueHKsXnf76Vs=
=k0v+
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/