This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: GDB on running process
- To: gnu-win32 at cygnus dot com
- Subject: Re: GDB on running process
- From: cgf at cygnus dot com (Christopher G. Faylor)
- Date: 1 Jul 1998 02:50:04 GMT
- Newsgroups: cygnus.gnu-win32
- Organization: Cygnus Solutions
- References: <199806300627_MC2-51B7-87DB.cygnus.gnu-win32@compuserve.com>
- Stamped: newsgate-cygnus
In article <199806300627_MC2-51B7-87DB.cygnus.gnu-win32@compuserve.com>,
Eric Proust <Eric_Proust@compuserve.com> wrote:
>I am trying to debug an interface program, that is launched by a particular
>software. I can attach GDB to the process and set a breakpoint, but when
>the breakpoint is about to be reached, I get a message saying "cannot
>access memory at address xxxxxx". It looks like NT doesnt allow to access
>memory between processes, which was to be expected (software at your
>fingertips....). But then, is there a way to go around this, or will I have
>to debug with printf statements ?
The code currently in gdb for attaching to running processes is not really
functional. I've made some changes to gdb to add the ability to attach
to running processes, as well as some support of threads and signals to
a local copy of gdb. Hopefully these changes will eventually make their
way back into the gdb sources.
If anyone wants to build gdb from scratch, I'll look into providing patches.
--
cgf@cygnus.com "Everything has a boolean value, if you stand
http://www.cygnus.com/ far enough away from it." -- Galena Alyson Canada
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".