This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC] Making target layers into a real stack
- To: "John S. Kallal" <jskallal at home dot com>
- Subject: Re: [RFC] Making target layers into a real stack
- From: Michael Snyder <msnyder at redhat dot com>
- Date: Thu, 12 Jul 2001 17:26:28 -0700
- CC: Andrew Cagney <ac131313 at cygnus dot com>, gdb-patches at sources dot redhat dot com, Michael Snyder <msnyder at cygnus dot com>, Mark Kettenis <kettenis at science dot uva dot nl>
- References: <01062017044600.01102@CyberMax> <3B3C0E2E.7040508@cygnus.com> <01071015192100.00894@CyberMax>
John S. Kallal wrote:
> My target layers patch was trying to address the immediate problems of
> the lin-lwp.c! For me the major problem is lin-lwp.c functions making direct
> calls to the child_target functions even when the child_target is not
> currently installed in the target stack.
>
> You can see the problems in the currently gdb snapshots by loading a
> LinuxThreads program in gdb then set gdb to the remote target. Most user
> command that follow will then be directed to the child_target functions even
> while though the child_target is inactive.
John, can I ask for more details and/or a specific testcase,
ie. a way to reproduce the behavior you describe? I have been
debugging a linux target with the remote protocol with some
success.