to its known failures and not complain about it in the future.
> On Sat, 6 Jul 2024 at 06:55, Thiago Jung Bauermann
> wrote:
>
> I ran your patch through a different CI loop that we have, where instead
> of using the distro's toolchain (binutils, gcc, glibc) to build and tes
Hello,
One more detail:
Thiago Jung Bauermann writes:
> I can see the problem reliably when running the testcase binary for -O1
> on an armv8l-linux-gnueabihf machine.
I ran your patch through a different CI loop that we have, where instead
of using the distro's toolchain (bi
Hello Paul,
Paul Richard Thomas writes:
> Hi There,
>
> I have been withholding the commit of this patch until I hear from you.
Sorry for the late response. I don't know much about Fortran or
gfortran, but I tried to have a look at the failure. More details below,
but unfortunately I didn't fin
Hello,
Rainer Orth writes:
> ci_not...@linaro.org writes:
>
>> In gcc_check master-aarch64 after:
>>
>> | commit gcc-15-937-g7e322d576eb
>> | Author: Rainer Orth
>> | Date: Fri May 31 09:29:38 2024 +0200
>> |
>> | testsuite: Adjust several dg-additional-files-options calls
>
Hello Andrew,
"Andrew Pinski (QUIC)" writes:
> These are all expected "failures" for arm (aarch32) really; the new testcases
> were known
> to fail for that target; it is recorded as PR 224847. I was not sure how to
> record this
> besides in the commit message.
Is the PR number correct? I ca
ci_not...@linaro.org writes:
> In CI config tcwg_kernel/gnu-master-arm-next-allyesconfig after:
>
> | commit v6.9-rc2-36-gfc4216add64ee
> | Author: Samuel Holland
> | Date: Fri Mar 29 00:18:28 2024 -0700
> |
> | drm/amd/display: use ARCH_HAS_KERNEL_FPU_SUPPORT
> |
> | No
Maxim Kuvyrkov writes:
> [CC: Thiago, for GDB crash]
Thanks!
> However, if I try to print "x", GDB crashes:
> ===
> (gdb) p x
> $2 = ( _data = (0x6568,
> /build/gdb-aPmCGS/gdb-12.1/gdb/value.c:856: internal-error:
> value_contents_bits_eq:
> Assertion `offset1 + length <= TYPE_LENGTH (val1->en
"H.J. Lu" writes:
> On Thu, Apr 4, 2024 at 6:18 AM wrote:
>>
>> We track this report status in https://linaro.atlassian.net/browse/GNU-1188
>> , please let
>> us know if you are looking at the problem and/or when you have a fix.
>>
>> In master-aarch64 after:
>>
>> | commit binutils-2_41-rel
Guinevere Larsen writes:
> On 13/02/2024 22:01, Thiago Jung Bauermann wrote:
>> Hello again,
>>
>> Thiago Jung Bauermann writes:
>>
>>> diff --git a/gdb/testsuite/gdb.threads/threadcrash.exp
>>> b/gdb/testsuite/gdb.threads/threadcrash.exp
>>
Hello again,
Thiago Jung Bauermann writes:
> diff --git a/gdb/testsuite/gdb.threads/threadcrash.exp
> b/gdb/testsuite/gdb.threads/threadcrash.exp
> index 3905ad6f9362..944fbcac1b18 100644
> --- a/gdb/testsuite/gdb.threads/threadcrash.exp
> +++ b/gdb/testsuite/gdb.threads/
Hello Guinevere,
Guinevere Larsen writes:
> I just checked out this regression but I think there's something odd going on
> in the setup
> that is running the tests. When I run the test locally, the relevant part of
> the logs
> looks like this:
>
> (gdb) PASS: gdb.threads/threadcrash.exp
Hello,
This is recorded as GDB bug #31254¹. I've been investigating it and
yesterday I realised it's a memory corruption issue in a data structure
used by the Arm unwinder which uses exception tables.
I hope to have a fix for it soon™.
¹ https://sourceware.org/bugzilla/show_bug.cgi?id=31254
M
Hello Nick,
ci_not...@linaro.org writes:
> In gdb_check master-arm after:
>
> | commit gdb-14-branchpoint-1244-gfad00902c24
> | Author: Nick Clifton
> | Date: Mon Jan 15 12:25:00 2024 +
> |
> | nm: Replace --with-symbol-versions with --without-symbol-versions in
> --help
Hello,
ci_not...@linaro.org writes:
> In gdb_check master-arm after:
>
> | 5 patches in gdb
> | Patchwork URL: https://patchwork.sourceware.org/patch/84201
> | 4a7c4c70418 Added docs
> | e50ecf9d8ee Add breakpointLocations request
> | 74f628035c8 Change gdb.LineTableEntry & Add gdb.lo
Hello Tamar,
Thank you for your clarifications. They're very helpful.
Tamar Christina writes:
>> - tcwg_bmk-code_size-cpu2017fast
>> - gnu-aarch64-master-O2: grew in size by 3% - 508.namd_r
>> - gnu-aarch64-master-O2_LTO: grew in size by 2% - 508.namd_r
>>
>> - tcwg_bmk-code_size-spec2k6
Hello Tamar,
It looks like this failure happens because qemu-aarch64 segfaults when
trying to run the testcase binary:
Running on qemu: timeout -k 30s 330s setarch x86_64 -R qemu-aarch64 -cpu any -R
0 -L
/home/tcwg-buildslave/workspace/tcwg_gnu_1/abe/builds/destdir/x86_64-pc-linux-gnu/aarch64
# TCWG CI
- Addressed Maxim's comments and submitted v4 of Abe change to always
add detected flaky tests to the flaky.xfail file, even if they are
already present in the baseline results.
- Wrote Ansible playbook to configure our bare metal machines.
- Analysed GDB on arm regressions GNU-1
Hello,
# TCWG CI
- Working on Abe change to always add detected flaky tests to the
flaky.xfail file, even if they are already present in the baseline
results. Sent a few versions of Gerrit review request already.
# [GNU-981] FEAT_GCS (Guarded Control Stack) support in GDB
- Prepared envir
Hello,
# [GNU-981] FEAT_GCS (Guarded Control Stack) support in GDB
- Started working on this feature. Currently adding ptrace and core file
support for the NT_ARM_GCS regset.
# Upstream community
- Implemented fix for ‘--with-auto-load-dir’ and
‘--with-auto-load-safe-path’ configure option
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Implemented support for expressing variable-sized vector registers in
the XML target description. Now making some changes in GDB's handling
of the expedited registers in the remote protocol and adjusting of the
g/
Hello,
# TCWG CI
- Flakiness in gdb.base/gdb-sigterm.exp causes false positives on
tcwg_check_gdb--master-arm-precommit, so started investigating its
failures.
- Investigated regressions reported by the CI:
- GCC regression GNU-935: Not a real regression, just already existing
failu
Hello,
Attended two events in a row in September, so had a bit of a time crunch
and the weekly report fell through the cracks...
# TCWG CI
- Investigated and fixed a few false positives in the GDB precommit CI
which were caused by random failures in
gdb.threads/process-dies-while-detaching
Guinevere Larsen writes:
> On 26/09/2023 18:04, Thiago Jung Bauermann wrote:
>> Hello Guinevere,
>>
>> Guinevere Larsen writes:
>>
>>> I got 3 of these messages about a patch I have upstream, which seems
>>> excessive.
>>> I also just
Hello Guinevere,
Guinevere Larsen writes:
> I got 3 of these messages about a patch I have upstream, which seems
> excessive.
> I also just managed to grab an aarch64 box and test it and got no errors, so
> I'd
> appreciate someone double checking that those werent 3 false positives please.
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Continuing work on new approach to support changing SVE vector length
in remote debugging. Fixed making native GDB work with the new
approach using the DWARF location expression. Now porting the same
approach to g
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Resumed working on new approach to support changing SVE vector length
in remote debugging. I was able to use DWARF location expressions in
the target description to express the SVE vector register sizes in
terms o
Hello,
# TCWG CI
- GCC regression GNU-884: Prathamesh confirmed that the new generated
code is better so I posted a patch adjusting the testcase.
- GCC regression GNU-885: Confirmed that the problem is still present in
trunk as of commit 829c0c06fe7b from yesterday, so opened bugzilla
11
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Continued working on new approach to support changing SVE vector
length in remote debugging.
# TCWG CI
- Analysed GCC regression GNU-880 which is actually an XFAIL → XPASS so
I sent a patch removing the xfail annot
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Returned to implementing support for changing SVE vector length in
remote debugging. The patch series I sent earlier this year used an
approach that some maintainers weren't enthusiastic about (modifying
the Remot
Hello,
# TCWG CI
- Implemented increasing testsuite timeout for each testsuite try in GDB
check jobs. Sent a Gerrit review request for it but then found out that
it makes armhf jobs take a lot longer, so abandoned it.
# Community
- Finished reviewing SME patches for GDB and gdbserver.
--
Hello,
# TCWG CI
- CI Babysitting: Worked on two regressions detected at the end of last
week.
- Enabled precommit testing for GDB patches.
# Misc
- Reviewing SME patches for GDB and gdbserver.
--
Thiago
___
linaro-toolchain mailing list -- lina
Hello,
# TCWG CI
- Babysat the CI: Investigated 9 regressions in GCC, 2 in GDB, 1 in LLVM
and 1 in glibc. Reported 4 in GCC (GNU-855, GNU-857, GNU-858 and
GNU-859). 3 of which are fixed and another has a tentative fix.
- Reviewed a couple of Gerrit requests.
--
Thiago
___
Hello,
# TCWG CI
- Changed tcwg_gnu-build.sh to apply GDB patch adding
'--with-additional-debug-dirs' option, and ABE's gdb.conf to use it.
Also changed both to add '--prefix /usr' option to GDB's configure.
Both changes to fix ld.so debug info issues in GDB testsuite runs on
armhf.
- T
Hello,
# TCWG Infrastructure
- Investigated why the CI didn't recover from empty gdb.sum, since it
was supposed to.
- Fixing validate_failures.py and tcwg_gnu-build.sh to correctly handle
empty gdb.sum.
- Fixing GDB armhf CI jobs to find distro's debug info.
# CI Babysitting
- Verified th
Hello,
# TCWG CI — GDB
- Investigated why the GDB check jobs stopped succeeding, as reported by
Maxim. It turns there was an upstream commit (which was soon reverted)
that broke generation of the gdb.sum file and consequently our
baseline results became empty. Theoretically the CI should r
Hello,
# TCWG CI — GDB
- Changed tcwg_gnu-build.sh to apply GDB testsuite patch to avoid infinite
loop in tcwg_gdb_check--master-arm jobs, while it isn't committed
upstream.
- Started investigating corrupt gdb.sum.1 file in
tcwg_gdb_check--master-arm jobs. I can't reproduce it by manually
Hello,
# TCWG CI — GDB
- Addressed review comments and sent v2 and v3 of the patch fixing loop
in gdb.reverse/step-reverse.exp. The testcase's original author gave his
Reviewed-by, now waiting for approval by a maintainer. In the meantime,
set up our CI to apply the patch locally.
- Sent
Hello,
# TCWG CI — GDB
- Continued investigating issue with GDB on armhf-linux about getting
SIGILL when trying to detect shared library loading/unloading. Noticed
that the problem happens only in tests that use the distro's toolchain
(either because they're for a language we don't build i
Hello,
# TCWG CI — GDB
- Investigating issue in CI jobs where touching all C files causes GDB
to show a warning about the source being newer than the executable.
This interferes with a few GDB tests.
- Continued investigating issue with GDB on armhf-linux about getting
SIGILL when trying
Hello,
# TCWG CI — GDB
- Analysed a number of potential regressions found by our CI on
aarch64-linux and armhf-linux. They aren't exactly regressions but bug
fixes or new features that work on other arches (or perhaps whose
testcases correctly detect PASSes on other arches) but not on
aa
Hello,
# TCWG Infrastructure
- Reviewed a bunch of Gerrit requests for our CI scripts.
- Finished job definition to run fast_check_{gcc,gdb} jobs triggered by
new Gerrit review requests for jenkins-scripts, benchmark scripts and
ABE. Sent Gerrit review request and now working on 2nd version
Hello,
# TCWG Infrastructure
- Reviewed a bunch of Gerrit requests for our CI scripts.
- Learning Jenkins job builder syntax and working on a job definition to
run fast_check_{gcc,gdb} jobs on Gerrit review requests for
jenkins-scripts and ABE.
- Changed CI scripts to save ABE and compone
Hello,
# TCWG Infrastructure
- Fixed problem in ABE with MinGW build of GDB's master branch.
- Fixed problem in upstream GDB with MinGW build of GDB's master branch.
- Analysed backlog of failed check_gdb jobs.
- A couple of "misbisected" commits, including one pointing to a glibc commit.
-
Hello,
[GNU-796] Stabilize GDB testsuite results in the CI
- Submitted to GDB mailing list and committed patches fixing the
gdb.asm/asm-source.exp regression found by the check_gdb job. Turned out
to be a small bug in the stabs debug format support.
- Committed Gerrit review request disabl
Hello,
[GNU-796] Stabilize GDB testsuite results in the CI
- Committed ABE change suggested by Maxim to mention failures that cause
additional testsuite runs.
- Tried to update Python MinGW build to 3.x, but it's a rabbit hole.
Proposing to disable Python support when cross-building GDB wit
Hello,
[GNU-796] Stabilize GDB testsuite results in the CI:
- Enabled gdb.gdb/unittest.exp in fast_check_gdb job. It should be
stable now that tcwg-jade-02's kernel has been upgraded.
- Enabled bisections for check_gdb jobs.
- Implemented Maxim's idea to handle GDB testsuite's tests that ca
Hello
Andrew Pinski writes:
>> - Investigated why cross-build gdbserver needs GMP and MPFR (and is thus
> failing to build) in tcwg-gnu-build jobs. Submitted Gerrit review
> request to fix it.
>
> This seems to be related to my change to the toplevel makefiles. Are
> you just building gdbs
Hello,
[GNU-796] Stabilize GDB testsuite results in the CI:
- Finished implementing ABE's support for rerunning failed tests using
Maxim's idea of leveraging validate_failures.py to determine which
tests need to be rerun. Submitted v3 and v4 versions, and committed
v4.
- Investigated why
Hello,
[GNU-796] Stabilize GDB testsuite results in the CI:
- Submitted and merged a couple of review requests removing obsolete CI
jobs related to release automation and release regression detection
- Finished version of scripts that have most of the logic for rerunning
testsuites in ABE.
Hello,
[GNU-796] Stabilize GDB testsuite results in the CI:
- Moved most of logic to rerun failed tests from tcwg_gnu-build.sh to
Abe and a new script based on the sum file parser of
compare_dg_tests.pl. The new script creates a "merged" sum file from
all the runs. Currently changing Abe
Hello,
# [GNU-796] Stabilize GDB testsuite results in the CI
- Cleaned up change in tcwg_gnu-build.sh that reruns failed tests and
created Gerrit review request¹.
- Based on Laurent's and Maxim's suggestions, decided to put the code which
retries the failed tests in Abe, so now I'm working o
Hello,
# [GNU-796] Stabilize GDB testsuite results in the CI
- Merged Gerrit review requests removing unsupported and flaky tests
from the fast_check_gdb CI job, and also one that makes it flag
regressions in the stable tests.
- Implemented change in Abe to build glibc with SystemTap probe
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Continued addressing review comments on v3 of the patches. Implemented
some of the suggestions in my local branch, and also engaged in
discussions.
# [GNU-796] Stabilize GDB testsuite results in the CI
- Fixed the
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- The patches were already reviewed by 3 maintainers, so started addressing
their review comments and answering questions.
- Committed first two patches in the series, which were self-contained code
improvements.
--
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Continued preparing patches for upstream submission. Did some final
code and testcase cleanups, updated/rewrote patch descriptions, wrote
the cover letter and the list of changes from v2.
- Posted the patches upstrea
Hello Laurent,
Laurent Alfonsi writes:
> Thiago,
>
> This is a false alarm.. Sorry about that.
No problem. Thank you for explaining the issue to me, and especially for
fixing it!
--
Thiago
___
linaro-toolchain mailing list -- linaro-toolchain@lis
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Continued preparing patches for upstream submission. Realised I had to
document my changes to the remote protocol in the GDB manual, so did
that. Also making small code cleanups and updating/rewriting patch
descrip
ci_not...@linaro.org writes:
> After gdb-13-branchpoint-527-g46758593515 commit
> 4675859351582f017b495ff13fb2ea72a99834af
> Author: Tom Tromey
>
> Rename to allow_ifunc_tests
This is a GDB commit so I had a look at this failure. The commit can't
be responsible for it though, because it o
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Fixed a regression found when preparing the new patches. Rebased on the
current mainline branch and continued preparing patches for upstream
submission.
# Misc
- Found a minor problem with a script in upstream GDB.
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Identified a regression on systems that do not support SVE. Debugged it
and now working on a fix.
--
Thiago
___
linaro-toolchain mailing list -- linaro-toolchain@lists.lin
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Finished implementing the new approach of sending new XML target
descriptions through the wire.
- Fixed a couple of minor regressions I introduced and rebased the code
on the current main branch.
- Now preparing the
# [GNU-767] Support changing SVE vector length in remote debugging
- Patches to gdbserver to support changing the SVE vector length: About
halfway through implementing the new approach of sending new XML
target descriptions through the wire.
# Misc
- Experimented with using a GDB wrapper t
# [GNU-767] Support changing SVE vector length in remote debugging
- Patches to gdbserver to support changing the SVE vector length: There
was an upstream discussion about whether changing the implementation
from relying on expedited registers to relying on sending target
descriptions over
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- v2 of the gdbserver patches to support changing the SVE vector length
was quickly reviewed by both Luis and Simon Marchi. I applied their
review suggestions and I'm now working on fixing a bug with
multi-threaded p
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Worked on v2 of the gdbserver patches improving SVE support. Found a
couple of simplifications that could be made to the code. Rebased on
current master branch and finished regression testing and patch
preparation.
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Working on v2 of the gdbserver patches improving SVE support. Found
and fixed a memory leak in my code while preparing patches for
upstream submission. Continuing preparing the patches.
# [GNU-796] Stabilise GDB tes
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Working on v2 of the gdbserver patches improving SVE support. Tested new
code for regressions in different systems and configurations and found
none. Preparing new version of the patches for upstream submission. Wil
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Confirmed that gdbserver doesn't send a new XML target description
over the wire when the vector length changes, so there's no impact of
these patches on the amount of remote protocol traffic, which was a
concern f
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Finished implementing Luis' idea of having a process-wide target
description in addition to the thread-specific one. Started checking
changes for regressions.
--
Thiago
Hello,
# [GNU-796] Stabilise GDB testsuite results in the CI
- Reworked and committed Gerrit change request for jenkins-scripts
adding a new CI job definition in tcwg_gnu-build.sh.
- Also reworked and committed another one to the same script adding a
default manifest file if one isn't speci
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Continued incorporating suggestions from Luis' review of the patches.
Working on a few regressions I introduced in the process.
# [GNU-796] Stabilise GDB testsuite results in the CI
- Started addressing Maxim's comm
Hello,
I haven't sent a report since week #36. For that reason, this report
covers three weeks.
# [GNU-796] Stabilise GDB testsuite results in the CI
- Implemented CI job to run fast GDB tests based on the list from
Sourceware's builder. Submitted Gerrit change requests for
jenkins-scripts
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Made a few last-minute adjustments to the code and fixed a couple of
regressions on x86_64-linux. Re-ran regression tests on x86_64-linux and
aarch64-linux. Wrote cover letter and descriptions for all the patches.
-
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Cleaned up code for upstream submission, and divided it into patches.
A couple of the patches affect other architectures and OSes, so made
sure the code builds on as many combinations I can test, and now doing
fin
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Finished fixing regressions in my changes to gdbserver for debugging an
inferior which changes the SVE length.
- Started cleaning up code for upstream submission and dividing it into
patches.
# Community participa
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- v2 of the patches fixing a small SVE bug when debugging in native mode
an inferior which changes the SVE length was committed upstream.
- Continued working on fixing regressions in my changes to gdbserver for
debug
Hello,
I noticed that I didn't send a report for week #30. Sorry about that. For
that reason, this report covers two weeks.
# [GNU-767] Support changing SVE vector length in remote debugging
- Prepared and submitted upstream a fix and a testcase for a small SVE bug
when debugging in native m
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Fixed last bug which prevented the sve-ioctls QEMU testcase to be
correctly stepped through in gdbserver. The next step is checking
whether any regression was introduced by my changes, and clean up the
code.
* In
Hello Mehdi,
Mehdi AMINI writes:
> I don't know if you are maintaining also clang-aarch64-sve-vla-2stage
> but it takes far too long right now (>10 hours).
Yes, I actually increased its ccache size on July 6th but only from 5 GB
to 20 GB because the machine running that builder is also a devel
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Rebased the actual SVE vector length changes on top of the stabilised
per-thread target descriptions changes. Now stabilising the result. Fixed
a couple of problems found when remote-debugging QEMU's sve-ioctls test
Hello David,
Thank you very much for your clarifications. They are very helpful.
Sorry for the delay in answering your message.
David Spickett writes:
>> There was a big impact on the flang builds on tcwg-jade-01 (which went from
>> 1h–2h to
>> 10min–30min), but not on other builds.
>
> Given
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Analysed and fixed a couple more regressions in my branch. The change to
per-thread target descriptions in gdbserver (which was the more
challenging part) is now free of regressions. Now cleaning up the part
that
Mehdi AMINI writes:
> On Wed, Jul 6, 2022 at 9:40 PM Thiago Jung Bauermann
> wrote:
>
> Mehdi AMINI writes:
>
> >> > On 29 Jun 2022, at 16:33, David Spickett
> >> wrote:
> >> >
> >> > What build times were you expecting to se
Hello,
I went through the LLVM build bots (and also the libc++ buildkites) and
increased their ccache max size. There was a big impact on the flang
builds on tcwg-jade-01 (which went from 1h–2h to 10min–30min), but not
on other builds. One reason is probably that since I made this change
earlier
Hello,
I looked into ccache usage on the LLVM build bots.
Mehdi AMINI writes:
> On Wed, Jun 29, 2022 at 3:39 PM Maxim Kuvyrkov
> wrote:
>
>> We have experimented with using zorg's CCACHE settings a few years back,
>> and it turned out to be more robust to configure ccache at the level of
>>
Hello,
# Linaro CI's GDB testsuite results
* Implemented new version of change in the Abe shell script to correctly
set auto-load-safe-path so that GDB can load libthread_db.so.1. Since
GDB's configure script needs to be passed an argument containing
literal dollar signs, use '@@' instead
Hello,
I just noticed that I didn't send a report for week #24. Sorry about
that. For that reason, this report covers two weeks.
# Linaro CI's GDB testsuite results
* Submitted upstream patch fixing gdb_compile regexp to account for our
GNATMAKE_FOR_TARGET value containing spaces. This should
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Debugged and fixed a few issues in my code where gdbserver was having
trouble with setting the target description for new threads. Also
fixed regressions in a couple more testcases.
# Linaro CI's GDB testsuite resu
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Debugged and fixed issues in my code where gdbserver was in some cases
trying to read inferior registers before aarch64_target was fully
initialised, and also while the inferior thread was running. This
improved r
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Found out that one issue I was having with gdbserver was caused by an
incompatibility it has with zsh (sourceware bug 26116).
* Fixed a gdbserver crash in my code where a register set was NULL in
the target descript
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
- Rebased my code on current master branch.
- Ran into issues with running the GDB testsuite against gdbserver, both
on my branch and on master. Currently investigating.
- Regarding the ptrace issues I'm running into, a
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Continued working on the testsuite regressions introduced by my code.
- Found out that the crash I was investigating (which happens when
gdbserver thinks that the kernel doesn't support SVE and crashes)
only oc
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Continued working on the testsuite regressions introduced by my code.
- Currently investigating a crash that happens when for some reason
gdbserver thinks that the kernel doesn't support SVE and crashes
while
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Continued working on the testsuite regressions introduced by my code.
- Realised that gdbserver uses “thread->tdesc != NULL” as a proxy of
whether it has already attached to the inferior process. My change to
t
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Found and fixed problem with the gdbserver prototype: it didn't clear the
registers cache when the target description changed. The prototype is
working now.
* Turned my attention to the testsuite regressions introduc
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Implemented prototype of GDB and gdbserver changing the target
description in sync when the vg pseudo-register changes. The GDB side
seems to be working, but gdbserver still has issues which I'm
currently debuggin
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Got prototype of variable length vectors in GDB target descriptions
barely working, but fell down a rabbit hole trying to fix an issue
with the vector register size being misreported by ‘sizeof()’. Decided
to change
Hello,
# [GNU-767] Support changing SVE vector length in remote debugging
* Moved tracking of this work from GNU-732 (GDB support for SME) to
more specific story GNU-767.
* Started writing prototype of variable length vectors in GDB target
descriptions.
# Basic setup / onboarding
- Read
Hello,
# [GNU-732] GDB support for ARMv9 Scalable Matrix Extension (SME)
* Continued working on gdbserver and remote protocol support for
programs that change the SVE vector length during execution:
- Studied the 2020 discussion around Luis' proposal to support changed
VL size in the R
Hello,
# [GNU-732] GDB support for ARMv9 Scalable Matrix Extension (SME)
* Continued reading patches from Mark Brown's v12 patch set adding SME
support to the Linux kernel. Sent a few trivial review comments.
* After conversation with Luis, decided to work on gdbserver and remote
protocol
1 - 100 of 124 matches
Mail list logo
