Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Ecilpse Debug views Refresh

Hi Eduard,


You can use ‘disconnect’ command for this purpose (This will disconnect the gdb connection only).

After this, you can use ‘target remote’ to establish a connection again.

[I think this won’t take that much time].


You can have a trial by giving commands ‘disc’ & ‘target remote: port_num’ from gdb console [it will refresh your debug views].


Please note that the AUTO_TERMINATE_GDB flag must be set as false [otherwise ‘disc’ command will terminate your GDB]


See the code snippet:


final IEclipsePreferences node = DefaultScope.INSTANCE.getNode(GdbPlugin.PLUGIN_ID);





Hope this will help you, even if it is a workaround[May be somebody can give other ideas as well].

Best Regards,



From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Bechtold, Eduard
Sent: Thursday, February 21, 2013 9:17 PM
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Ecilpse Debug views Refresh


Hello dear Eclipse-Team,


Since long we have been using Eclipse for debugging our targets. We have also implemented many Plug-Ins for internal purposes.

Some of our Plug-Ins use gdb commands to change Information on our targets.

We have encountered one problem when changing something that affects the current debug context with gdb commands.

·         In one of our Plug-Ins we change the current program counter, stack pointer… and after these changes we would like Eclipse to notice it. We need Eclipse to refresh like when receiving suspend event from gdb after hitting a breakpoint, when debugging.

·         In an other Plug-In we change one of our target settings, which is called thread awareness. When it is turned off we only return the active thread to the debugger (for faster debugging). Otherwise we return information of all running threads. Here we have the same problem as above, we need some mechanism to tell Eclipse it should refresh again on current debug context.

Currently we are using many workarounds only for that purpose. For example inserting a breakpoint and jumping that address. Other workarounds contain even replacing instructions with nops and letting the target run over them, so that the target suspends again and the gdb sends the suspend trigger for refresh of Eclipse.

So my question is:

·         Is there some way to trigger a refresh of the internal Eclipse Debug views (including debug, registers, variables, expressions view…)?

      (For example by sending an event with the active debug context, and/or active launch)


We would really appreciate your help with our Eclipse refresh problem, so we can get a rid of a whole bunch of workarounds.


With best regards,
Eduard Bechtold

Siemens AG
Industry Sector
Industry Automation Division
Industrial Automation Systems
Factory Automation
Werner-von-Siemens-Str. 50
92224 Amberg, Germany

Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Gerhard Cromme; Managing Board: Peter Loescher, Chairman, President and Chief Executive Officer; Roland Busch, Brigitte Ederer, Klaus Helmrich, Joe Kaeser, Barbara Kux, Hermann Requardt, Siegfried Russwurm, Peter Y. Solmssen, Michael Suess; Registered offices: Berlin and Munich, Germany; Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322

***** Confidentiality Statement/Disclaimer *****

This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt.
The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message.

Back to the top