Patch for changing the values of registers via the CPU Register window

[MicroSourceCode]

An experimental patch for changing the values of registers via the CPU Register window. AVR and STM32. The project must be created through a standard wizard project: ARM project, AVR project.

The patch does not affect the debugging of other languages, the window for changing the register value appears only if you debug AVR or STM32 microcontrollers. Made for Unix users, Windows users can use EmBlocks, etc.

Download:
https://github.com/MicroSourceCode/cb20.03-cpuregisters

[ollydbg]

An experimental patch for changing the values of registers via the CPU Register window. AVR and STM32.

The patch does not affect the debugging of other languages, the window for changing the register value appears only if you debug AVR or STM32 microcontrollers. Made for Unix users, Windows users can use EmBlocks, etc.

You post the same thread twice?

[BlueHazzard]

I like this,
some comments:
1) the patch seems to contain some *.orig files. I think they are wrong?
2) Why only linux? Are there some limitations for windows machines (system calls?), or simply not tested?
3) in general Is it possible to modify cpu register also on x86?
4) Can you post this on source forge? Here it will get lost...

[MicroSourceCode]

1. Erroneous inclusion of the file.
2. It should also work in Windows, I didn't check it.
3. Yes it is possible, the meaning of this? When using C++ or C, you will see incomprehensible data, due to the code optimizer.
4. SourceForge = github.com. SourceForge is a very ancient mammoth. Github has a search and in general it is better.

[Miguel Gimenez]

He is referring to the C::B ticket site, hosted in Sourceforge:

https://sourceforge.net/p/codeblocks/tickets/

[MicroSourceCode]

He is referring to the C::B ticket site, hosted in Sourceforge:

https://sourceforge.net/p/codeblocks/tickets/

Thank you for the explanation.

[AndrewCot]

The following wiki page has info on creating the patch and submitting it via sourceforge.
    https://wiki.codeblocks.org/index.php/Creating_a_patch_to_submit_(Patch_Tracker)


To save you pulling your hair out w.r.t. SVN usage I use the following to generate a patch file that can be submitted:

1. git svn clone --revision 12579 http://svn.code.sf.net/p/codeblocks/code/trunk
2. Copy the trunk so you have a backup
3. Update the code in trunk
4. Stage any new files
5. git diff git-svn --unified --no-prefix --output=changes.patch


It looks like the patch file you created may not have the correct directory references to be applied to the SF SVN repo. You can check by applying the patch in step 3 above to see if the patch is okay or not.

Edit: Make the link work