On 09/05/12 12:16, Stian Skjelstad wrote: >>>> perhaps there is a way to determine the version of gdb at runtime, >>>> and act appropriately? >>> .. >>>> Thoughts? >>> >>> Please investigate the above, and if you will then please do it fast, >>> to get this resolved now. >> >> I looked at this a while back, and AFAICT version information of any kind > is not a part of the protocol. The closest you seem to come is the > qSupported packet, but this works the wrong way around (i.e., >gdb querying > the server). > > We could forward a patch to gdb to interpret a qSupported or similar command > for how a "g" register command should be formatted, or detection of arm-abi.
I think it is too late for addressing this issue at the gdb end; the old gdb versions will be around for a while, as will the current, so the problem will continue to exist for some time. OpenOCD should probably have a configure time option indicating which version of gdb to build for and/or a command line argument to override the default; this would somewhat alleviate things at the user end. Tomas ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
