delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
X-Authentication-Warning: | modi.xraylith.wisc.edu: khan owned process doing -bs |
Date: | Sun, 14 Mar 1999 17:49:22 -0600 (CST) |
From: | Mumit Khan <khan AT xraylith DOT wisc DOT edu> |
To: | Kai-Uwe Rommel <rommel AT ars DOT de> |
cc: | cygwin AT sourceware DOT cygnus DOT com |
Subject: | Re: B20: cannot debug a program with GDB that has been linked with -ladvapi32 |
In-Reply-To: | <C1256734.0072F369.00@abraham.ars.de> |
Message-ID: | <Pine.SUN.3.93.990314174826.1967A-100000@modi.xraylith.wisc.edu> |
MIME-Version: | 1.0 |
On Sun, 14 Mar 1999, Kai-Uwe Rommel wrote: > > If one compiles/links a program that uses a call from the Win32 > advapi32.dll (such as GetUserName), it cannot be debugged with > gdb. When gdb attempts to debug such a program, the program crashes. Can you possibly put together the smallest testcase that exposes this problem? This will be very helpful if we were to try and find a workaround ala IBM. Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |