This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] No resuming while tfinding
- From: Stan Shebs <stan at codesourcery dot com>
- To: tromey at redhat dot com
- Cc: Stan Shebs <stan at codesourcery dot com>, gdb-patches at sourceware dot org
- Date: Thu, 18 Mar 2010 10:46:54 -0700
- Subject: Re: [PATCH] No resuming while tfinding
- References: <4BA0377C.1040000@codesourcery.com> <m3k4t939b8.fsf@fleche.redhat.com>
Tom Tromey wrote:
Does return_command also need to call ensure_not_tfind_mode?
It seemed less necessary, because it doesn't resume, it just scribbles
on the stack - in tfind mode the target kicks it back with write errors.
The previous discussion has gotten me to wondering whether it would be a
good idea to allow the user to write into a trace buffer. While it
sounds crazy at first, it can make sense for the same reasons that it
does in a live target; you have a hypothesis about how an expression
calculates out, stuff the hypothesized value in memory, and print the
expression.
It's a little more farfetched that return would be useful if writing
worked; if you had collected enough stack, you would see a backtrace
displayed as if the return had been done, but since you can't resume,
the exercise seems pointless.
Stan