[Bashdb-devel] Fwd: Documentation on interaction with bashdb

[niXman <i.n...@gm...>]

Please tell me, commands for bashdb and other of your debuggers, are
identical? That is a front-end can work with all of your debuggers?

Regards.

2011/12/8 Rocky Bernstein <ro...@gn...>:
> On Thu, Dec 8, 2011 at 12:17 AM, niXman <i.n...@gm...> wrote:
>>
>> Hi Rocky!
>>
>> I want to write in C++/Qt front-end for bashdb.
>> Where can I get documentation on the interaction with bashdb?
>
>
> The best place to start is the documentation, the reference guide that comes
> with the distribution. You can also find it online at
> http://www.rodericksmith.plus.com/outlines/manuals/bashdbOutline.html
>
> What DDD and the emacs front-end (and I image the Eclipse front end) do is
> send commands and parse output that comes back from the debugger. This is
> not an ideal way to go, but, largely, I don't know of a better way to do
> things.
>
> To reduce unnecessary polling, a while back there was an "annotation" mode
> added to bashdb. The idea is that when rather than have the front-end query
> for information to see if something has changed, the debugger would by
> default post information when there is a change. For example when there is a
> change to the stack. To use that, there is the debugger command  "set
> annotate 1". The annotation output is prefaced by two null characters after
> a newline; after that is the kind of output, "stack" or "breakpoints". The
> older emacs front end that came with bashdb used that.
>
> I've since been rewriting this Emacs front end to support lots of debuggers,
> I don't use that anymore. But having worked a little bit on the front ends
> has made me more sensitive about  providing information that front-ends can
> use. That is why when bashdb leaves, it gives a termination message. Or why
> when you set a breakpoint a message comes back indication that the
> breakpoint was set and where it was set.
>
> Lastly I should also mention that there is --tty option to bashdb that tells
> it what tty to use for debugger input and output. The intent is to be able
> to more easily separate debugger input and output from debugged program
> input and output.
>
> Good luck and let me know when you come up with something.
>
>
>
>
>>
>>
>> Thank you.
>>
>>
>> ------------------------------------------------------------------------------
>> Cloud Services Checklist: Pricing and Packaging Optimization
>> This white paper is intended to serve as a reference, checklist and point
>> of
>> discussion for anyone considering optimizing the pricing and packaging
>> model
>> of a cloud services business. Read Now!
>> http://www.accelacomm.com/jaw/sfnl/114/51491232/
>> _______________________________________________
>> Bashdb-devel mailing list
>> Bas...@li...
>> https://lists.sourceforge.net/lists/listinfo/bashdb-devel
>
>