bug#30151: Debugger API

[james@jojojames.com]

Hi Stefan,

Please close it! I don’t think there is enough interest from any one party to keep it open.

Thanks!

> On Sep 28, 2019, at 3:56 PM, Stefan Kangas <stefan@marxist.se> wrote:
> 
> James Nguyen <james@jojojames.com> writes:
> 
>> Thanks, I've submitted an issue here -> https://github.com/realgud/realgud/issues/206.
>> 
>> Looking at some old code I did when adding breakpoints for lldb, it looks like I just used the marker-filter and matched against strings in the filter looking for 'breakpoint print' strings and extracting the info out after.
>> 
>> That might be similar to how something like flymake/flycheck runs a *something* in a separate process and then matches strings against the output to get the error output out.
>> 
>> E.g. http://ix.io/EsZ (meant just for discussion)
>> 
>> I'm not sure how we can better support this flow (or if it's even a good idea) but from what I've seen the marker-filter is the one place where we can 'extract' information from the underlying debugger (using its output).
> 
> Did anything ever come out of your investigations and experiments?  We
> sure would welcome contributions and improvements to gud.el.
> 
> As it stands however, this is an open issue in our bug tracker, but I
> can't really make out what it is concretely about.  Should this issue
> perhaps be closed?
> 
> Best regards,
> Stefan Kangas