Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [dsdp-dd-dev] Console vs UI

Hi Marc,
My only goal when porting the console support from CDI-MI to DSF-MI was to achieve feature parity. 

I really love the idea of a command line interface to the debugger, however to make it really useful I think we would need more support from GDB.  The problem is that the Command Line Interface (CLI) commands and their results are opaque to the debugger integration.  I.e. when user changes a variable using the console, there is no MI-protocol event generated to tell the debugger to refresh.  So what we would need from GDB is more events to notify the UI of target state changes including:
- target running (there is a stopped event, but not running)
- breakpoints changed
- memory changed
- registers changed
- thread started/exited.

It is possible to work around the lack of these events, by having the debugger integration parse all the CLI commands being sent, and to simulate the these event.  Some of this was actually implemented by CDI-MI (and ported to DSF-MI).  But it's a pretty complicated workaround which would probably never be fully complete.

There are also other issues with the CLI interface, but this is the biggest non-starter.


Marc Khouzam wrote:
within discussions on the GDB mailing list there was a question about the DSF console.
I played around with it and issued commands and I noticed that we don't do anything in the UI
when commands are given that way.
For example, chaning the value of an _expression_ or setting a breakpoint from teh console (command-line)
did not show in the UI.
I was wondering what our goal was for the console?


Marc Khouzam
Software Designer, Methods and Tools


Ericsson Canada Inc

8500 Decarie Blvd.
H4P 2N2, Mont-Royal, Qc, Canada

Office: +514 345 7900 x42350
Fax: +514 345 6159
Mobile: +514 951 7191
Email: Marc.Khouzam@xxxxxxxxxxxx

Ce courriel est confidentiel et uniquement destiné à son ou ses destinataires. Il est défendu de le consulter, de l'utiliser, de le dévoiler ou de le diffuser sans autorisation. Si ce message vous est parvenu par erreur, merci d'en aviser l'expéditeur par retour de courrier et de le détruire sans le divulguer.  Un courriel et ses pièces jointes peut être sans autorisation corrompu, interrompu, amendé, altéré et infecté. L'entreprise ne reçoit et n'envoie de courriel qu'avec l'entente qu'elle n'est responsable d'aucune corruption, interception, modification, altération, infection ou conséquence possible.

This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you.  E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.


_______________________________________________ dsdp-dd-dev mailing list dsdp-dd-dev@xxxxxxxxxxx

Back to the top