This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: RFC GDB Linux Awareness analysis
- From: Doug Evans <dje at google dot com>
- To: duane at duaneellis dot com
- Cc: Peter Griffin <peter dot griffin at linaro dot org>, Andreas Arnez <arnez at linux dot vnet dot ibm dot com>, gdb <gdb at sourceware dot org>, Lee Jones <lee dot jones at linaro dot org>
- Date: Mon, 5 Oct 2015 12:40:53 -0700
- Subject: Re: RFC GDB Linux Awareness analysis
- Authentication-results: sourceware.org; auth=none
- References: <20151005115437 dot 5c1bb9f86d671edec44bb378f25c04cc dot 28494d3874 dot wbe at email03 dot secureserver dot net>
On Mon, Oct 5, 2015 at 11:54 AM, <duane@duaneellis.com> wrote:
> duane> 7) A good example of scripting is during postmortem debug
> duane> GDB cannot call (execute) a helper function within the
> duane> target because the target is not âliveâ
>
> doug> Depends on what the helper function does of course.
> doug> E.g., it's possible to resurrect a corefile (assuming it hasn't
> been
> doug> truncated, etc.) enough to run a pretty-printer contained in the
> doug> app (as opposed to in python).
>
> Yes, as you said "it depends on what it does"
And it depends on the debugging environment.
> I would say almost categorically you *cannot* use the target pretty
> printer.
Whatever. It was just an example.
> Every target is different, every embedded system is different.
>
> Some of these pretty print problems also occur when live debugging.
>
> This whole area is one giant rat hole of problems to make work
> universally.
I think you'll find you're preaching to the choir here.