Re: Buildbot failure - clang-arm64-windows-msvc

Hi Julian, Thanks for reporting this issue. Let me build and test your commit offline and get back to you. -- Omair Javaid www.linaro.org On Sun, 29 Sept 2024 at 03:50, Julian Schmidt wrote: > I decided to revert back to green again. Your insights would be great to > have this patch

Re: C++ standard library for build bot clang-armv8-lld-2stage

On Mon, 1 Jul 2024 at 14:56, David Spickett wrote: > This is one for @Omair Javaid who is on bots > this week. > > But to save him some confusion, I noticed that the next build > https://lab.llvm.org/buildbot/#/builders/122/builds/151 passes. This is > because > https:/

Re: clang-aarch64-sve-vls-2stage workers

Hi Vitaly, Thanks for pointing out the bad buildbot worker. We were already looking into the issue and I have now stopped the worker until it's fixed. Apologies for inconvenience! -- Omair Javaid www.linaro.org On Mon, 1 Apr 2024 at 22:19, Vitaly Buka wrote: > Looks like one wor

Re: LLVM buildbot clang-aarch64-full-2stage

Hi Orlando, Thanks for getting in touch. I have just approved your zorg pull request. Please request Galina Kistanova gkistan...@gmail.com for buildbots restart once you merge your changes to zorg. On Fri, 22 Mar 2024 at 17:25, orlando.hy...@sony.com wrote: > Hi, > > I noticed this address r

Re: Flang buildbot workers

/175 https://lab.llvm.org/buildbot/#/builders/191 https://lab.llvm.org/buildbot/#/builders/173 https://lab.llvm.org/buildbot/#/builders/181 PS: http://llvm.validation.linaro.org/ is still showing old builders a patch has been merged so it will be updated soon. Omair Javaid www.linaro.org On Thu

Re: Flang buildbot workers

I just checked there are 160 cores on the machine and all bots are running well above 100%. There has been a master update recently so some bots have changed names meaning and I guess new worker build directories will be formed for all affected. Omair Javaid www.linaro.org On Wed, 23 Jun 2021

Re: Many of your builders are red for long time

scussed in > >> https://reviews.llvm.org/rGb2851aea80e5 . I hope to get windows > >> builders green by end of this week. > >> > >> Hi Galina, > >> > >> linaro-armv8-windows-msvc-01 and -02 are in good shape now: > >> - http://la

Re: GDB: etm traces decoding and breakpoints for arm targets

helps. -- Omair Javaid www.linaro.org On Mon, 2 Nov 2020 at 15:06, Zied Guermazi wrote: > > hi, > > while testing the implementation in gdb of branch tracing on arm > processors using etm, I faced the the situation where a breakpoint was > set, was hit and then the execution

Re: Please make lldb-aarch64-ubuntu non-flaky, or stop it from sending email / irc pings

Hi Nico, We have investigated lldb-aarch64-ubuntu buildbot's intermittently test failures. They seemed to be triggered by https://reviews.llvm.org/D83904 We have committed a fix https://reviews.llvm.org/D85514 We regret the inconvenience this may have caused. Thanks! -- Omair J

[ACTIVITY] 27 - 31 March 2017

=== This Week === GDB Kernel Awarenes - Kernel Dump setup for ARM [9/10] -- Background study on kdump and try to find working steps for QEMU ARM. -- There is a problem with kdump-tools install script with QEMU -- Tried building kernel for Raspberry Pi2 and Pi3 with kdump, no success so far. -- Se

[ACTIVITY] 20 - 24 Feb 2017

=== This Week === LLDB ARM/AArch64 hardware breakpoints [TCWG-717] [3/10] -- Fixed issues identified during review. -- Investigation of thumb32 vs thumb16 mode selection for arm hw breakpoints. -- Committed upstream. LLDB BUD17 Presentation [6/10] -- Created demos -- Wrote slides Miscellaneous A

[ACTIVITY] 13 - 17 Feb 2017

=== This Week === LLDB ARM/AArch64 hardware breakpoints [TCWG-717] [6/10] -- Test on Arm hardware and fix issues. -- Wrote breakpoint command based test-cases for multi-thread tests. -- Wrote RSP packets based test-cases. -- Code clean-up, formatting and re basing to latest code. -- Submit final p

[ACTIVITY] 6 - 10 Feb 2017

=== This Week === LLDB ARM/AArch64 hardware breakpoints [TCWG-717] [9/10] -- Submitted AArch64 hardware breakpoint patch for review. -- Updates after upstream comments. -- Added Arm hardware breakpoint support code. -- Testing and debugging of Arm code on android arm device. Miscellaneous Activit

[ACTIVITY] 30 Jan - 3 Feb 2017

=== This Week === LLDB ARM/AArch64 hardware breakpoints [TCWG-717] [9/10] -- Wrote multi-threaded implementation of hardware breakpoints. -- Added thread specific handlers to create hardware breakpoints. -- Basic multi-threaded test application works after some fixes and debugging. -- Committed fi

[ACTIVITY] 23 - 27 January 2017

=== This Week === LLDB ARM/AArch64 hardware breakpoints [TCWG-717] [6/10] -- Fixed hardware breakpoints routines in LLDB AArch64 register context. -- Code tweaks in NativeProcessLinux/NativeThreadLinux/ProcessGDBRemote -- Hardware breakpoint working with single threaded applications -- Submitted a

[ACTIVITY] 16 - 20 January 2017

=== This Week === Investigate LLDB testsuite failures on Pine64 target (AArch32 and AArch64 modes) [TCWG-1012] [4/10] -- Capture tests leaving behind runaway processes, found 3 so far. -- Capture random failures and mark them flakey. ARM/AArch64 hardware breakpoints [TCWG-717] [5/10] -- Code revi

[ACTIVITY] 09 - 13 January 2017

=== This Week === Monitor LLDB buildbot for minimum down time. [TCWG-712] [1/10] -- LLDB Arm build was broken and then fixed upstream but a buildbot script bug. -- Fixed buildbot script to make sure not every type of build is refreshed after a breakage. Investigate LLDB testsuite failures on Pine

[ACTIVITY] 02 - 6 January 2016

=== This Week === Back from month long holiday had a surgery during this period. Add Pine64 as tester to LLDB buildbot [TCWG-1011] [3/10] -- Configure Pine64 with Ubuntu 16.04 image -- Configure network on Pine64 to be used with LLDB buildbot -- Configure Pine64 for AArch32 mode execution -- Conf

[ACTIVITY] 06 - 10 June 2016

=== This Week === Support for watchpoint un-alligned watchpoint addresses on LLDB AArch64 [TCWG-367] [3/10] -- Implementation successful without the need for instruction emulation. -- Watchpoint hit detection fixed with ptrace reporting hit address correctly. -- Used up watchpoint HitAddress funct

[ACTIVITY] 30 May - 03 June 2016

=== This Week === Investigation of Nexus devices kernel issues.[TCWG-622] [6/10] -- Figured out source trees for various android devices and checked out kernel code. -- Comparison between watchpoint implementation of different kerenel sources supported by Nexus devices. -- Figured a way to burn a

[ACTIVITY] 23 - 27 May 2016

=== This Week === Resolved TCWG-231 (LLDB bring up and bug fixing on HiKey 96Board) [TCWG-231] [1/10] -- Ran tests on AArch64 LLDB tests on HiKey and compared with Nexus 9 test results. -- Less than 1% difference in test results and good pass rate found. LLDB ARM: Bug fixes, integration and testi

[ACTIVITY] 16 - 20 May 2016

=== This Week === Support for watchpoint un-alligned watchpoint addresses on LLDB AArch64 [TCWG-367] [3/10] -- Made changes to NativeRegisterContext_arm64 to support multiple watchpoint slot for a single watch address. -- Enabled unaligned watchpoints and experimented with resulting false positive

[ACTIVITY] 09 - 13 May 2016

=== This Week === Enable LLDB testsuite to show zero failures on Hikey 96 Board (AArch64 Linux) [TCWG-231] [4/10] -- Ran multiple builds and testsuite runs to figure out latency issues. -- Investigated remaining failures and submitted appropriate bugzilla bugs. -- Committed xfails upstream. Supp

[ACTIVITY] 18 - 22 April 2016

== Progress == LLDB Chromebook Test Stability [TCWG-563] [3/10] -- Failures reduced to 15 fails and 4 errors after fixing stepping bug. -- Investigated remaining issues some of them are known issues and others will need further investigation. LLDB ARM Thread Stepping Problem [TCWG-566] [5/10] -

[ACTIVITY] 11 - 15 April 2016

== Progress == LLDB Buildbot Setup [TCWG-241] [1/10] -- Created a new factory for LLDB buildbots. Halted plan to migrate till turning chromebook build green. LLDB Chromebook Test Stability [TCWG-563] [3/10] -- Investigated some failures some of them were fixed by a systemZ support large patch s

[ACTIVITY] 4 - 8 April 2016

== Progress == LLDB Buildbot Setup [TCWG-241] [9/10] -- Migration of local master/slave setup to Linaro LLVM lab. -- Setup slave to be able to connect to chromebook for lldb remote testing. -- Modified Android build scripts to work with chromebook in llvm lab. Miscellaneous [1/10] -- Meetings, e

[ACTIVITY] 8 - 12 February 2016

== Progress == LLDB development -- Handling aggregate types return values on arm-linux-gnueabihf ABI. Patch review and committed upstream. [TCWG-228] [1/10] -- Debugging of stepping issues on chromebook (arm hard float ABI) [TCWG-230] [2/10] -- Progress on vector return values and aggregate types

[ACTIVITY] 1 - 5 February 2016

== Progress == LLDB development -- Committed patch fixing return value handling on arm-linux-gnueabihf [TCWG-228] -- Finished work on handling aggregate types return values on arm-linux-gnueabihf ABI. [TCWG-228] [5/10] -- Submitted single and double precision handlers for upstream review. [TCWG-22

[ACTIVITY] 25 - 29 January 2016

== Progress == LLDB development -- Submitted patch fixing return value handling on arm-linux-gnueabihf [TCWG-228] [5/10] -- float and double types handled in above patch did some more investigation for handling structs [TCWG-228] [2/10] -- Collecting LLDB status data, ran testsuite on different ha

[ACTIVITY] 18 - 22 January 2016

== Progress == LLDB development -- Debugging of return value related issue coming up on chromebook ARM [TCWG-228] [2/10] -- Setup of Arm testing on AArch64 using chroot on highkey [TCWG-231] [1/10] -- Investigation of failures when setting watchpoint on vector variables [TCWG-231] [4/10] Miscell

[ACTIVITY] 11 - 15 January 2016

== Progress == LLDB development -- Triage testsuite failures on AArch64 highkey [TCWG-231] [5/10] -- Triage testsuite failures on chromebook (armel) [TCWG-228] [3/10] Miscellaneous [2/10] -- Meetings, emails, discussions etc. -- Documents preparation for Thailand visa == Plan == LLDB developme

[ACTIVITY] 4 - 8 January 2016

== Progress == LLDB development -- Fixed thumb mode issues if user triggers changes to PC register [TCWG-228] [3/10] -- Triage of testsuite failures on armel chromebook [TCWG-228] [2/10] -- Update xfail decorators for arm-linux targets. Marked traiged as xfail. [TCWG-494] [3/10] Miscellaneous [1/

[ACTIVITY] 9 - 13 November 2015

== Progress == LLDB development -- Root Google Nexus devices and read debug module configuration with kernel module [TCWG-429] [7/10] -- Figure out steps to unlock and root Nexus S -- Figure out steps to build kernel and kernel module for Nexus S -- Tried out lldb watchpoints with custom

[ACTIVITY] 12 - 16 October 2015

== Progress == LLDB development -- Verify LLDB watchpoints on Android Arm and AArch64 targets. [TCWG-405] [4/10] - Ran LLDB testsuite on Nexus5, Nexus 7, Nexus S and Nexus 9 devices. - Started into failing watchpoint tests on all devices. -- Investigate and fix LLDB watchpoints tests that

[ACTIVITY] 7 - 11 September 2015

== Progress == LLDB development -- Progress to add support for un-alinged watchpoints on AArch64 [TCWG-367] [5/10] -- Truncating watched bits wasnt accepted as a solution, will look into issues during connect. -- Trying to figure out a way to use multiple watchpoint slots for a single watchpoint.

[ACTIVITY] 31 August - 4 September 2015

== Progress == LLDB development -- Testing and bug fixing lldb on hikey AArch64 [TCWG-231] [4/10] -- Looking into multi-threaded watchpoint test failures on AArch64 highkey board. -- Fixed watchpoint installation lag and unexpected behaviour. Submitted http://reviews.llvm.org/D12522 --

[ACTIVITY] 24 - 28 August 2015

== Progress == LLDB development -- Testing and bug fixing lldb on hikey AArch64 [TCWG-886] [7/10] -- Improve error handling of AArch64 watchpoint code. Submitted, got reviewed and committed http://reviews.llvm.org/D12328 -- Looked into ways to improve watchpoint installation lag. -

[ACTIVITY] 17 - 21 August 2015

== Progress == LLDB development -- Testing and bug fixing lldb on hikey AArch64 [TCWG-886] [2/10] -- Looked into watchpoint tests which are still failing after committing watchpoint support and bug fixes. -- Modifications to arm hardware breakpoint and watchpoint support [TCWG-770] [TCWG-79

[ACTIVITY] 10 - 14 August 2015

== Progress == LLDB development -- Testing and bug fixing lldb on hikey AArch64 [TCWG-886] [7/10] -- Submitted following fixes and got them reviewed -- http://reviews.llvm.org/D11899 -- http://reviews.llvm.org/D11902 -- http://reviews.llvm.org/D11987 Miscellaneous [3/10] -- Meeti

[ACTIVITY] 3 - 7 August 2015

== Progress == LLDB development -- Testing and bug fixing lldb on hikey AArch64 [TCWG-886] [9/10] -- Debugging of watchpoint test failures and problems with multiple watchpoints. -- Clean-up of AArch64 watchpoint code and fixing watchpoint cache bugs. Miscellaneous [1/10] -- Meetings, emails,

[ACTIVITY] 27 - 31 July 2015

== Progress == LLDB development -- Setup lldb test debug environment for testing failing tests on chromebook. [1/10] -- Debug various lldb hang scnarios on chromebook for armhf support [TCWG-855] [4/10] -- Figure out alternate fix for http://reviews.llvm.org/D11129. [TCWG-855] [3/10] Miscellan

[ACTIVITY] 06 - 10 July 2015

== Progress == LLDB development -- Debugging problems with process launch and debugserver crash on remote connection. [TCWG-855] [6/10] -- Caught the notorious issue mentioned above fix can be found here http://reviews.llvm.org/D11129. -- Figured arm lldb and lldbserver host builds on chromebo

[ACTIVITY] 29 June - 03 July 2015

== Progress == LLDB development [TCWG-855] [8/10] -- Figure out build steps for building cross lldb-server with arm-linux-genueabihf-g++ -- Debugging of lldb-server communication packets for fixing lldb-server armhf crash problem. -- Comparison with androidabi version to figure out missing piec

[ACTIVITY] 22 - 26 June 2015

== Progress == LLDB development -- Support for running lldb on arm hard float abi targets [TCWG-855] [7/10] -- Built lldb-server for armhf trusty chromebook -- Figured out problem with lldb-server showing up i386-linux-gnu as target triple. -- Verfied load of arm-elf executable and breakp

[ACTIVITY] 11 - 15 May 2015

== Progress == LLDB development -- Submitted and committed AArch64 hardware watchpoint/breakpoint support [2/10] [TCWG-771] -- Submitted Arm hardware watchpoint/breakpoint support [1/10] [TCWG-770] -- Debugged arm watchpoints on Nexus 7 Android device. [2/10] [TCWG-651] Miscellaneous [5/10]

[ACTIVITY] 4 - 8 May 2015

== Progress == LLDB development -- Finished most of work for ARM watchpoints and hardware breakpoints [3/10] [TCWG-770] -- Added hardware breakpoint handlers for AArch64 [1/10] [TCWG-771] -- Debugging for ARM watchpoints not hitting the hardware watchpoint Set/Clear handlers. [3/10] [TCWG-770]

[ACTIVITY] 27 April - 1 May 2015

== Progress == LLDB development -- Wrote hardware breakpoint handlers for NativeLinuxRegisterContext ARM [2/10] [TCWG-770] -- Debugging for issues and code cleanup AArch64 LLDB watchpoint support [2/10] [TCWG-771] -- Fix, test, debug, cleanup and patch re-submission. [1/10] -- Resubmitted

[ACTIVITY] 20 - 24 April 2015

== Progress == LLDB development -- Debugging test code for hardware breakpoint/watchpoint issues on chromebook for ARM LLDB support [4/10] [TCWG-770] -- Wrote native process linux helpers for arm and aarch64 hardware breakpoints [2/10] [TCWG-770] [TCWG-771] -- Fix, test, debug, cleanup and patc

[ACTIVITY] 13 - 17 April 2015

== Progress == LLDB development -- Some progress on hardware watchpoint support for lldb arm linux. [1/10] [TCWG-770] -- Some progress on hardware watchpoint support for lldb aarch64 linux. [1/10] [TCWG-771] -- LLDB ARM SysV ABI implementation. [4/10] [TCWG-643] - Testing and updates with

[ACTIVITY] 6 - 10 April 2015

== Progress == LLDB development -- Patch update, test and re-submission native Linux register context for Arm. [1/10] [TCWG-650] -- Patch update, test and re-submission POSIX register context for Arm. [1/10] [TCWG-755] -- Tested lldb armhf native build on ubuntu utopic, build fine but lacks of

[ACTIVITY] 30 March - 3 April 2015

== Progress == LLDB development -- Completed implementation and submited native Linux register context for Arm upstream [3/10] [TCWG-650] -- Completed implementation and submitted POSIX register context for Arm upstream [3/10] [TCWG-755] -- Fixing LLDB build and dev environment issues [1/10]

[ACTIVITY] 23 - 27 March 2015

== Progress == LLDB development -- Patch submission and build testing LLDB Arm SysV ABI classes [1/10] [TCWG-643] -- Patch submission and build testing LLDB AArch64 SysV ABI classes [1/10] [TCWG-715] -- Implemented native Linux register context for Arm [3/10] [TCWG-650] -- Implemented POSIX re

[ACTIVITY] 16 - 20 March 2015

== Progress == LLDB development -- Implemented LLDB Arm SysV ABI classes [3/10] [TCWG-643] -- Implemented LLDB AArch64 SysV ABI classes [3/10] [TCWG-715] -- Started implementation of Arm native register context [1/10] [TCWG-650] -- Figure out steps to run lldb-remote testsuite on Arm and AArch

Re: [ACTIVITY] 9 - 13 March 2015

I am writing them here: https://wiki.linaro.org/WorkingGroups/ToolChain/LLDB Shouldnt these be public? On 17 March 2015 at 15:13, Renato Golin wrote: > On 17 March 2015 at 00:42, Omair Javaid wrote: >> -- Written wiki pages for LLDB developer process [1/10] > > Where? > &g

[ACTIVITY] 9 - 13 March 2015

== Progress == LLDB development -- Got lldb-server executable running on aarch64 target but debug connection not working [1/10] [TCWG-640] -- Got lldb-server executable running on arm target [1/10] [TCWG-641] -- Started collecting missing pieces for arm lldb linux run control support [2/10]

[ACTIVITY] 2 - 6 March 2015

== Progress == LLDB Development -- Tried lldb-server cross build for AArch64 target on x86 host [1/10] [TCWG-640] -- Tried lldb-server cross build for ARM target on x86 host [4/10] [TCWG-641] GDB Development -- Started writing tests for arm-gdb instruction recording [3/10] [TCWG-677] -- S

[ACTIVITY] 23 - 27 Feburary 2015

== Progress == LLDB development -- Some code sniffing and created JIRA cards with some task estimation [2/10] -- Trying AArch64 cross build and update howto [1/10] -- Trying Arm cross build and update howto [2/10] GDB patch updates and test cases for ARM record-replay instruction recording

[ACTIVITY] 16 - 20 January 2015

== Progress == LLDB development -- LLDB Call graph analysis for understanding some development nits [1/10] -- Trying out LLDB server arm and aarch64 cross compilation. [2/10] -- List down arm-lldb task list with some debugging [2/10] Miscellaneous [1/10] -- 96board setup Holiday [4/10]

[ACTIVITY] 19 - 23 January 2015

== Progress == LLDB vs GDB investigation [TCWG-583] [4/10] -- Scoring of previous patches and mailing list discussions -- Tried and was able to build+test lldb on x86_64 linux -- Tried and was able to build (but not test) lldb on arm linux -- Tried lldb AArch64 build but couldnt get it going succe

[ACTIVITY] 12 - 16 January 2015

== Progress == LLDB vs GDB investigation [TCWG-583] [2/10] Configuration of GDB AArch64 remote testing with juno. [1/10] GDB AArch64/ARM/X86 native/remote testing and comparison result compilation. [4/10] Investigate some record-replay testsuite failures on d01. [2/10] Miscellaneous [1/10] -

[ACTIVITY] 8 - 12 December 2014

== Progress == QEMU kernel debugging setup [3/10] [TCWG-568] -- Finally figured out the steps to debug kernel with ARM cortex A9 core. Kernel debugging to investigate limitation of ARM watchpoint implementation [2/10] [TCWG-569] -- Debug kernel code with gdb to investigate problems. Miscella

[ACTIVITY] 1 - 5 December 2014

== Progress == QEMU kernel debugging setup [5/10] [TCWG-568] -- Setup arm Linux kernel debugging to debug watchpoints GDB with cygwin build/testing process [2/10] -- Figured out GDB build and test procedure on cygwin. Miscellaneous [3/10] -- Meetings, Emails etc -- Hong Kong visa applica

[ACTIVITY] 24 - 28 November 2014

Apology for sending this out late. == Progress == Debugging ARM gdb watchpoint failures [4/10] [TCWG-567] -- Prepared a testsuite patch for unsupported tests on ARM -- Investigation of other failures due to watchpoints installation rejected through ptrace interface. QEMU kernel debugging set

[ACTIVITY] 10 - 14 November 2014

== Progress == Environment setup, installations, board setup etc [4/10] -- Prepared a local dev machine to work with in absence of lab. -- Prepare panda board for gdb on android testing. -- Figure out SSH failure issues with gdb testsuite runs. -- Try out foundation model for android testi

Re: [Question] Should gdb client query FP registers even if gdb server does not report having org.gnu.gdb.aarch64.fpu feature?

There was discussion to put with-expat in default config options not sure if that has been done or not. On 11 November 2014 13:39, Will Newton wrote: > Do we know if the Windows gdb binary links against expat? Without > expat XML support is disabled. > > On 11 November 2014 06:51,

[ACTIVITY] 3 - 7 November 2014

== Progress == AArch64 work on tracepoints and watchpoints failures [4/10] -- Review of AArch64 debug hardware architecture -- AArch64 debugging/testing stalled due to lab down time -- Tried compiling and running custom AArch64 kernel with foundation model Work on some arm specific fix of r

Re: [Question] Should gdb client query FP registers even if gdb server does not report having org.gnu.gdb.aarch64.fpu feature?

PU > supporting. > For now, I added some code in our code to return the value of fpsr and fpcr > to make the gdb client happy. > > Regards, > Strong > > -Original Message- > From: Omair Javaid [mailto:omair.jav...@linaro.org] > Sent: Monday, November 10

Re: [Question] Should gdb client query FP registers even if gdb server does not report having org.gnu.gdb.aarch64.fpu feature?

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

[ACTIVITY] 27 - 31 October 2014

== Progress == GDB Tracepoints/Fast Tracepoints support on arm [TCWG-480] [3/10] -- Investigate arm hardware debugging capabilities in linux kernel. ARM/AArch64 GDB testsuite failures investigation [TCWG-507] [4/10] Trying out patches that add support for gdbserver catch vfork/fork [TCWG-507]

[ACTIVITY] 20 - 24 October 2014

== Progress == Further progress on GDB Tracepoints/Fast Tracepoints support on arm [TCWG-480] [6/10] -- Debugging and trying out some code enabling tracepoints in gdbserver -- Research on past tracepoint patches and x86 vs arm architecture comparison ARM/AArch64 GDB testsuite failures investi

Re: Q about using AArch64 gdb with target running in AArch32 state

On 21 October 2014 12:51, Peter Maydell wrote: > On 17 October 2014 16:28, Qu, Strong wrote: >> For our use case, we are running the gdb client at early state of boot. So >> the ARMv8 target might be running into any EL and into either AArch64 or >> AArch32 state. My questions are: >> >> 1)

[ACTIVITY] 13 - 17 October 2014

== Progress == Catch up with work after return from Eid ul Adha and Annual Holidays [7/10] * Hong Kong visa application * UPS repairs and office cleanup * Catching up with work, gdb roadmap and open/running cards. * Emails/Patch scrolling/Meetings etc * Sick day off on Monday GDB Tracep

[ACTIVITY] 1 - 5 September 2014

== Progress == Debug KGDB with gdb for testing [4/10] LCU14 slides preparation and study for presentation. [2/10] Miscellaneous [4/10] * Configure to use hackbox to test aarch64 gdb remote configs * Retrieve gdb test results in different configurations. * Emails/Patch scrolling/Meetings et

[ACTIVITY] 25 - 29 August 2014

== Progress == Arm gdb record-replay pending patches up-streaming [3/10] * Update, test and resubmit patches AArch64 gdb record-replay patches up-streaming [3/10] * Update, test and resubmit patches Miscellaneous [4/10] * Configure git for replying to previous patch submission using send e

[ACTIVITY] 18 - 22 August 2014

== Progress == GDB Tracepoints/Fast Tracepoints support on arm [TCWG-480] [4/10] * FAST tracepoints try out on arm chromebook with trampoline code borrowed from kernel. AArch64 gdb record-replay bug fix [TCWG-503][TCWG-498] [2/10] * Debugging of issues Miscellaneous [4/10] * Reading on Pre

[ACTIVITY] 11 - 15 August 2014

== Progress == Arm gdb record-replay bug fix [4/10] [TCWG-314] * Testing of all patches on x86 and arm machines. * Patch submission upstream after sync up with latest gdb trunk. AArch64 gdb record-replay bug fix [3/10] [TCWG-503][TCWG-498] * Debugging of testsuite failures with apm and foun

[ACTIVITY] 4 - 8 August 2014

== Progress == BeagleBoard and Pandaboard setup for gdb testing [3/10] * Deployed debian linux on both boards * Installation of required packages for gdb testing * Run gdb native tests on Beagleboard, Pandaboard and Chromebook Arm gdb record-replay bug fix [6/10] [TCWG-314] * Applied prev

[ACTIVITY] 28 July - 1 August 2014

== Progress == BeagleBoard and Pandaboard setup for gdb testing [1/10] * Got both alive and working with minimal os * Trying ubuntu prebuilt binaries didnt work. Out of office to get internet fixed and buy accessories for boards. [1/10] Eid Public Holidays in Pakistan from 29th July till 1st

[ACTIVITY] 18 - 25 July 2014

== Progress == GNU Tools Cauldron * Some useful corridor meetings with various GNU tools developers and maintainers. TCWG Sprint [8/10] * Got to meet the team and discuss TCWG roadmap. * Some useful howtos specially back porting and patch review howtos. * Sprint with ARM and useful discus

[ACTIVITY] 14 - 18 July 2014

== Progress == * On Holiday from 14th to 17th July 2014. * Travel to Cambridge to attend TCWG Sprint and GNU Tools Cauldron on Friday 18th July. == Plan == * Attend GNU Tools Cauldron 18th to 20th July. * Attend TCWG Sprint 21st to 24th July. * Friday 18th July return back after attending TCW

[ACTIVITY] 7 - 11 July 2014

== Progress == * Testing and Analysis of testsuite failures in arm-linux-gdb [TCWG-509] [6/10] -- Run ARM GDB testsuite on local chromebook, remote chrombook and pandaboards. -- Investigation of failures on arm. * AArch64 GDB handling of functions with empty prologue. [TCWG-504] [1/10] -- S

[ACTIVITY] 30 June - 4 July 2014

== Progress == * AArch64 GDB reverse watchpoints issue. [TCWG-503] [4/10] -- Found a new fix in generic process record implementation. Testing stalled by too many 2500 failures seen on arm-linux-gdb in general and some 850 record/replay implementation. * AArch64 GDB handling of functions with

[ACTIVITY] 23 - 27 June 2014

== Progress == * AArch64 GDB reverse watchpoints issues. [TCWG-503] [6/10] -- Proposed a fix which failed testing now working on an alternate fix in gdb process record target implementation. * Further progress on AArch64 GDB handling of functions with empty prologue. [TCWG-504] [2/10] -- Anal

[ACTIVITY] 16 - 20 June 2014

Sorry for sending this late this week. == Progress == * Ran gdb testsuite on arm and x86. Investigated failures on arm-native-gdbserver config. [2/10] * Investigate shared library gdb test failures with dejagnu on remote connections. [TCWG-504] [2/10] * Debug AArch64 GDB reverse watchpoints iss

[ACTIVITY] 09 - 13 June 2014

== Progress == * GDB arm v8 record/replay -- Investigated prologue analysis and stepping issues. [3/10] [TCWG-484] -- Updates to JIRA cards. -- Updates to patches stalled till next week. * GDB arm v7 record/replay -- Prepare SIMD instruction recording support patches for re submission. [1

[ACTIVITY] 02 - 06 June 2014

== Progress == * GDB arm v8 record/replay -- Fixed issues showing up when building code with default optimization. [TCWG-484] [3/10] -- Fixed failures in until-reverse test cases. [TCWG-484] [1/10] -- Investigation of failures in watchpoint-reverse and solib test cases. [TCWG-484] [2/10]

[ACTIVITY] 26 - 30 May 2014

== Progress == * GDB arm v8 record/replay -- Support for recording advance SIMD load store instructions. [TCWG-403] [4/10] -- Code cleanup and patch creation. [2/10] -- Investigation of patches failing in native configuration. [TCWG-484] [2/10] * Miscellaneous -- Sick day off on Monday [2

[ACTIVITY] 19 - 23 May 2014

== Progress == * GDB arm v8 record/replay -- Completed implementation of system call recording [TCWG-409] [4/10] -- Support for recording A64 Loads and stores [TCWG-409] [2/10] -- Bug Fixing to reduce failures in gdb.reverse testsuite [TCWG-484] [2/10] * Miscellaneous -- Day off on Friday

[ACTIVITY] 12 - 16 May 2014

== Progress == * GDB arm v8 record/replay -- Bug fixing: Improve gdb.reverse testsuite results on armv8 [TCWG-451] [2/10] -- core files issue submitted bfd patch upstream [TCWG-451] -- Support for recording Data processing - Advanced SIMD and Cryptographic [TCWG-405] [TCWG-407] [3/10] -- S

[ACTIVITY] 5 - 9 May 2014

== Progress == * GDB arm v8 record/replay: core files issue [TCWG-451] [6/10] -- Add bfd support for missing aarch64 core file handlers. -- Added regset caching functions for aarch64 linux gdb. * GDB arm v8 record/replay: Support for recording A64 Data processing - Floating point instructions

[ACTIVITY] 28th April - 2nd May 2014

== Progress == * GDB reverse debugging on aarch64 -- Further progress on decoding of aarch64 load store instructions. [TCWG-401] [1/10] * Investigated and progressed towards fix for GDB unable to read core files [TCWG-451] [6/10] * Public Holiday on 1st May [2/10] * Miscellaneous [1/10] --

[ACTIVITY] 21 - 25 April 2014

== Progress == * GDB reverse debugging on aarch64 -- Complete decoding of aarch64 data processing immediate instructions. [TCWG-399] [1/10] -- Complete decoding of aarch64 data processing register instructions. [TCWG-402] [1/10] -- Completed decoding of aarch64 exception and system instructi

[ACTIVITY] 14 - 18 April 2014

== Progress == * GDB reverse debugging on aarch64 -- Scored through a64 instruction set details. [1/10] -- Completed testing and implementation of all basic structures. [TCWG-398] [1/10] -- Started decoding aarch64 load store instructions for recording. [TCWG-401] [2/10] -- Completed decod

[ACTIVITY] 7 - 11 April 2014

== Progress == * GDB reverse debugging on aarch64 [6/10] [TCWG-398] -- Setup development tree and debug environment. -- Verified generic reverse debugging implementation aarch64. -- Implemented main function stubs to catch instruction for decoding and recording. * Work on gdb testing utilit

[ACTIVITY] 31 March - 4 April 2014

== Progress == * Work on gdb testing utility [TCWG-96] [8/10] -- Support to run native and native-gdbserver test via ssh on remote machines like arm-linux. -- Bug fix and test gdb testing utility by running it various configurations. -- Update wiki page with testing utility and how to use it

[ACTIVITY] 24 - 28 March 2014

== Progress == * Short Week -- Monday Day Off: Pakistan Day 23rd March public holiday roll over. [2/10] -- Short leave on Thursday [1/10] * Work on gdb testing utility [TCWG-96] [7/10] -- Writing a new gdb testing utility script that automates gdb testing in various configurations and compa

[ACTIVITY] 17 - 21 March 2014

== Progress == * Add support for fork/vfork/exec events/catchpoints in remote gdbserver [TCWG-263] [4/10] -- Debugged catchpoint code and reviewed gdbserver implementation for events. -- Still require a lot of code understanding before actual implementation can start. * Wrote a script that ta

[ACTIVITY] 10 - 14 March 2014

== Progress == * Get started with Aarch64 GDB testing and development process using foundation model. [6/10] [CARD-1115] -- Figured out steps for running gdb in remote mode using foundation model. -- Wrote a wiki page with steps on development process, still in progress. -- Completed a gdb t

[ACTIVITY] 23 - 28 Feburary 2014

== Progress == * Completed testing and submitted patches upstream. [TCWG-251] [TCWG-252] [1/10] * Travel to capital Islamabad for Macau visa follow up. [3/10] * Shifting to new office space and setting up office [6/10] == Plan == * Study aarch64 code and create task breakdown for record/replay

[ACTIVITY] 10 - 14 Feburary 2014

== Progress == * Updated, tested and re-submitted patch for arm native watchpoint/hwbreak rework. [2/10] * Updated, split-up and tested patches for process record ASIMD, VFP etc support. [TCWG-251] [TCWG-252] [3/10] * Tried setting up gdb for aarch64, no luck yet. [TCWG-389] [1/10] * Investigat

  1   2   >