This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/586: Can't debug a 'V' program in gdb due to relocation errors.
- From: robertlj at yahoo dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 26 Jun 2002 17:53:05 -0000
- Subject: gdb/586: Can't debug a 'V' program in gdb due to relocation errors.
- Reply-to: robertlj at yahoo dot com
>Number: 586
>Category: gdb
>Synopsis: Can't debug a 'V' program in gdb due to relocation errors.
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Jun 26 10:58:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Robert Jacobs
>Release: GNU gdb 5.0 (20010428-3)
>Organization:
>Environment:
gdb configured as i686-pc-cygwin
Windows NT 4.00.1381
Using cygwin downloaded june 2002.
V source downloaded june 2002.
>Description:
When I try to debug a sample 'V' program compiled for for use
in the win32 gui library and try to debug it, I get the following
errors from gdb.
LDR: Automatic DLL Relocation in vdraw.exe
LDR: Dll Wbhook32.dll base 11c00000 relocated due to collision with Dynamically Allocated memory
LDR: Dll msh_zwf.dll base 0d2d0000 relocated due to collistion with Dynamically Allocated Memory
After I get all these Windows messages to dissapear, When I try press the stop sign on the top left of gdb, I get the following.
No response from target. Detach from target (and stop debugging it)? Yes No.
Thanks in advance for your time.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: