|
|
|
|
| Re: Failure to execute MI command during Debug - Helios [message #1723824 is a reply to message #1723812] |
Thu, 18 February 2016 09:35   |
David Vavra
Messages: 1426
Registered: October 2012 |
Senior Member |
|
|
It's been a long time since I've used Helios (even my older systems have Juno) but my recollection is the option is there somewhere, perhaps on a different tab. I don't recall having to attach to a running task though.
Stopping at main might not be what is going on. It may be an entirely different issue. There is a console window for GDB (two actually) selectable through a drop down menu in the Console View. It may give some indication what GDB (or Eclipse through GDB) is trying to do.
Check the .gdbinit file. There may be something in it that is triggering it. If there is, trying to attach while running GDB by itself would also have the same problem. Have you tried running GDB by itself and try to attach?
Yes, do upgrade if you can.If you can't, try to keep the tools originally used by Helios intact or you may find yourself facing compatibility problems.
EDIT:
Still can't type.
[Updated on: Thu, 18 February 2016 09:40] Report message to a moderator |
|
|
|
|
|
|
| Re: Failure to execute MI command during Debug - Helios [message #1723869 is a reply to message #1723845] |
Thu, 18 February 2016 15:42 |
 Marc Khouzam
Messages: 357
Registered: July 2009 |
Senior Member |
|
|
Jonah Graham wrote on Thu, 18 February 2016 12:51Quote:Actually the link given by the OP (https://www.eclipse.org/forums/index.php/t/795327/) does say there is one.
That link is referring to remote connection (i.e. C/C++ Remote Application), different flow than attach (i.e. C/C++ Attach to Application).
An example of remote is when connecting to gdbserver (or something else implementing RSP, such as Segger)
Right. When doing a "C/C++ Application" or "C/C++ Remote Application" type of launch, CDT will actually start the process for you and therefore, the user can specify if CDT should stop the process at "main" (or whatever other method you choose).
For "C/C++ Attach to Application" CDT is being asked to attach to a running process. In that case, it does not make sense to have an option to "stop on startup" since the process is already running.
Now, the error
-target-attach 28175
Error message from debugger back end:
Cannot access memory at address 0x5f31534b52455361
is caused by GDB. I'm not sure what it is trying to do exactly, but it seems that it cannot attach to the process for some reason.
If this happens again with a newer version of Eclipse, I would recommend trying manually with GDB to see if your target even allows to attach to a process.
Marc
|
|
|
|
|
| Re: Failure to execute MI command during Debug - Helios [message #1789932 is a reply to message #1723869] |
Thu, 31 May 2018 22:00 |
Gregg Wonderly
Messages: 3
Registered: May 2018 |
Junior Member |
|
|
Actually, it still does not work. The problem is that the --attach doesn't have a correct argument implementation. There should just be a checkbox labeled "Attach to Pid: " with the ability to enter the PID to attach to. That should in turn cause the "download app" to be unchecked, and the requirement for a working remote path to the executable to be voided. Right now, there are a couple of ways to get a valid command line, that I found, but none are allowing the debugging session to actually work. Oxygen is confused.
You can add --attach to the "Gdbserver options:" field on the Gdbserver Settings sub tab of the Debugger tab, and then either put the PID after the port number (then you see this error above), or you can place the PID in the "Remote Absolute file Path for C/C++ Application:" field on the Main tab.
In this last case, it shows connected and their are "stop" buttons active, but no "pause" or "resume" buttons. The Debug pane doesn't show any thread details either, so its really not working.
|
|
|
Powered by
FUDForum. Page generated in 0.04086 seconds
] 
Search
Help
Register
Login
Home
