embedded system and "target remote"

Matthias Pfaller leo@marco.de
Tue Nov 8 10:31:00 GMT 2016


I'm currently implementing gdb server support for our cortex-m3/m4 based
embedded systems.

At the moment I have the following things working:
- reading and writing memory
- reading and writing registers
- thread info
- stopping/resuming threads
- single stepping a thread

At the moment I'm implementing break points using the FPB unit.

I would like to setup the FPB unit at context switch time for thread
specific break points. Is there a way to pass the referenced thread id
with the 'Z' commands?

Is there a way to modify the behaviour of the break point commands to
always reference the currently selected thread? Gobal breakpoints do not
make sense in my usage case.

Another thing I'd really like to do is to enforce non-stop and
target-async from the target side. Is there a way to do this?

regards, Matthias

PS: How does gdb recoginze the initial stack frame? At the moment stack
trace backs of stopped threads will not stop at correct frame.
Matthias Pfaller                          Software Entwicklung
marco Systemanalyse und Entwicklung GmbH  Tel   +49 8131 5161 41
Hans-Böckler-Str. 2, D 85221 Dachau       Fax   +49 8131 5161 66
http://www.marco.de/                      Email leo@marco.de
Geschäftsführer Martin Reuter             HRB 171775 Amtsgericht München

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4349 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://sourceware.org/pipermail/gdb/attachments/20161108/fe67c92d/attachment.p7s>

More information about the Gdb mailing list