RE: [cdt-dev] CDT debugging with 16-bit addressable memories

[Edwin Steiner <Esteiner@xxxxxxxxx>]

Hallo John!

Thanks for your fast reply.

Actually we are not using gdb but a custom debugger which implements the
gdb/mi interface. We added the addressable unit size as an extra field that
gdb does not report, i.e. the response by our debugger would look like this
(line breaks for readability):

    ^done,addr="3000",bits-per-addressable-unit="16",memory=[
    {address="0xbb8",data=["0xfffd","0x0","0x567","0xbba"]},
    {address="0xbbc",data=["0x0","0xb","0x0","0x0"]},
    {address="0xbc0",data=["0x300a","0x400b","0x500c","0x600d"]}],
    next-page="3012",next-row="3004",nr-bytes="12",total-bytes="12"

(With 'bits-per-addressable-unit="16",' being the non-standard part.)

While the gdb/mi spec explicitly allows the producer to add fields, I guess
the CDT code base would require a more general approach. Or would such an
addition be acceptable?

I could also look into possibilities of specifying the addressable unit size
in the launch configuration.

Which would be the preferable way to get the size info all the way down to
(or up to) the MemoryBlock?

best regards

Edwin

This e-mail is strictly confidential and intended only for use by the addressee(s) unless otherwise indicated.