This is the mail archive of the cygwin@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: B20: cannot debug a program with GDB that has been linked with -ladvapi32
- To: Kai-Uwe Rommel <rommel@ars.de>
- Subject: Re: B20: cannot debug a program with GDB that has been linked with -ladvapi32
- From: Mumit Khan <khan@xraylith.wisc.edu>
- Date: Sun, 14 Mar 1999 17:49:22 -0600 (CST)
- cc: cygwin@sourceware.cygnus.com
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- In-Reply-To: <C1256734.0072F369.00@abraham.ars.de>
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- Sender: cygwin-owner@sourceware.cygnus.com
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@sourceware.cygnus.com