Bug 389984 - JTAG Startup commandos are not executed after continue/jump
Summary: JTAG Startup commandos are not executed after continue/jump
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: Next   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-20 05:38 EDT by Eduard Bechtold CLA
Modified: 2020-09-04 15:21 EDT (History)
5 users (show)

See Also:


Attachments
Patch for cdt 8.1.0 (631 bytes, application/octet-stream)
2012-09-20 05:38 EDT, Eduard Bechtold CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eduard Bechtold CLA 2012-09-20 05:38:27 EDT
Created attachment 221288 [details]
Patch for cdt 8.1.0

During the launch of a GDB Hardware debugging session using standard debug launcher all commands defined in Startup Tab's initialization commands of the launch config after the first continue/jump are ignored and not executed.

To reproduce:
Create a GDB-Hardware-Debugging JTAG-launch config using standard debug launcher containing jump/continue command(s) in initialization commands.

A simple example:

// Initialization commands
break endofbootloader
load bootloader.elf //load bootloader application which sets up memory/tlb/...
...                 //do some settings
jump startofbootloader
// now bootloader runs and stops on breakpoint set above
load application.elf // now we can load the actual application to be debugged

// Run commands
jump startofapplication //start the application


The attached patch file is a quick solution for this problem. Although its flaw is a possible endless loop.