This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: backtrace/1784: GDB dynamically activated to perform stack tracebacks
- From: Andrew Cagney <ac131313 at redhat dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 29 Sep 2004 16:18:03 -0000
- Subject: Re: backtrace/1784: GDB dynamically activated to perform stack tracebacks
- Reply-to: Andrew Cagney <ac131313 at redhat dot com>
The following reply was made to PR backtrace/1784; it has been noted by GNATS.
From: Andrew Cagney <ac131313@redhat.com>
To: gdb-gnats@sources.redhat.com
Cc:
Subject: Re: backtrace/1784: GDB dynamically activated to perform stack tracebacks
Date: Wed, 29 Sep 2004 12:12:59 -0400
> Considering gdb has remoting interfaces, would I be able to create a new communication environment that would communicate to itself ? Is this too much of a stretch for gdb ?
Nope!
Have you looked at creating a `target self' that examined memory from
the running process, and registers from an in memory jmp_buf?
Andrew