Re: RFC GDB Linux Awareness analysis
Doug Evans <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <CADPb22S0xonReJ-J1-mV+v2NZGHMw=q7NJSiGG_n2qybjbzjrg@mail.gmail.com> |
On Mon, Oct 5, 2015 at 11:54 AM, <[email protected]> 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.