|DSF - GDB: Console view for application being debugged [message #1747422]
||Mon, 14 November 2016 14:56
| Jim Adams
Registered: July 2009
I have a CDT based IDE that was using the CDI to implement a gdb debug session for debugging an ARM processor via a jtag connection. With Neon dropping support for CDI, I am migrating the code to DSF-GDB. The CDI implementation would open three console views when a session was launched. One for gdb, one for OpenOCD / QEMU, and one for the application being debugged. If the application then printed output (e.g. printf), the output would show up in it's console view.|
With the DSF-GDB implementation, only two console views are opened, one for gdb and one for OpenOCD / QEMU. There is no console view for the application being debugged. When the application executes a printf statement the output does not get displayed.
I have a class that extends org.eclipse.cdt.debug.gdbjtag.core.GDBJtagDSFFinalLaunchSequence. GDBJtagDSFFinalLaunchSequence is responsible for connecting the gdb session started by org.eclipse.cdt.dsf.gdb.launching.FinalLaunchSequence to the jtag device connected to the hardware. With the old, CDI based code, when gdb is remotely connected to the target the console view was created. In the new code it is not created.
I can open a console view but I cannot find the application process to associate with the console view. The only processes I get from my launch object are the OpenOCD / QEMU and the gdb? Are there any suggestions on how I can get the third console view associate with the application output?
Powered by FUDForum
. Page generated in 0.01866 seconds