Have you implemented a qXfer packet response if not you can do so to
use xml description provided by target.
Here is a gdb help link that describe how to client can query target.xml.
https://sourceware.org/gdb/onlinedocs/gdb/Retrieving-Descriptions.html#Retrieving-Descriptions
On 10 November 20
== Progress ==
* Pushed malloc microbenchmark to glibc (1/10, TCWG-160)
* Upstream work (4/10, CARD-341)
- glibc patch review (C11 atomics series)
- glibc patchwork cleanup
* Look into binutils input fuzzing fixes (1/10)
* Investigate ARM port of lld (2/10)
* Email, meetings, review, etc. (2/10)
Thanks, Omair. I did check xml files in Linaro's source
(gdb-linaro-7.6.1-2013.10). In the target.xml file our gdb server sends back to
gdb client, we only include regsiters X0~X30, sp, pc and cpsr. It's close to
gdb-linaro-7.6.1-2013.10\gdb\features\aarch64-core.xml, which is included in
aarch
== Progress ==
Bug 404 [5/10]
Bugs 403/418 [2/10]
Misc [3/10]
. office move
. review
___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain
cbuild2 benchmarking - TCWG-360 [4/10]
* SPEC 2006 cross-built binaries now running. Easy when you know how.
libm exercising - CARD-1693 [4/10]
* Understood improved libm usage on 1 benchmark.
* Tried 3 more. 1 shows significantly more time in libm on AArch64 over AArch32.
Meetings/mail/etc - [2/
== Issues ==
* none.
== Progress ==
* GCC 4.9 and 4.8 2014.11 (1/10)
- Reviewed FSF branch Merges.
* Lab move (3/10)
- Cherry-picked cbuildv2 master patches in schroot-test
- Created a new jenkins job to tst the "schroot lab move" branch
- The job is able to build all the targets but val
On 7 November 2014 02:27, Qu, Strong wrote:
> Hello,
>
>
>
> We have implemented gdb server in one of our project and we are using Linaro
> aarch64-none-elf-gdb.exe as gdb client. Our gdb server will response to
> packet 'qXfer:features:read:target.xml:0,fff' with a xml file which only
> claims fe
