profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/saagarjha/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Saagar Jha saagarjha @twitter Cupertino, California https://saagarjha.com <optimized out>

iina/iina 27970

The modern video player for macOS.

ish-app/ish 10458

Linux shell for iOS

Jintin/Swimat 1447

An Xcode formatter plug-in to format your swift code.

evilpenguin/ARMRef 192

ARM Assembly Reference Manual for iOS, iPadOS, and macOS.

jusleg/OpenAdblock 56

iOS Content Blocker adblock

ofekih/SimpleHtmlRenderer 3

APCS SimpleBrowser

ahjragaas/glibc 2

Unofficial mirror of the GNU C Library, updated every 10 minutes.

apple-open-source-mirror/scripts 2

Scripts to download projects and tag their releases

iina/Just 2

Swift HTTP for Humans

push eventahjragaas/busybox

Ron Yorston

commit sha 56f0e886db0543a27f369d7f95eb9da2fb3d069c

cal: implement -m Some people prefer the week to start on Monday. Add the '-m' option to support this. function old new delta cal_main 926 966 +40 day_array 316 337 +21 packed_usage 34151 34158 +7 .rodata 99224 99225 +1 ------------------------------------------------------------------------------ (add/remove: 0/0 grow/shrink: 4/0 up/down: 69/0) Total: 69 bytes Signed-off-by: Ron Yorston <rmy@pobox.com> Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>

view details

push time in 2 hours

push eventsaagarjha/binutils-gdb

Nick Clifton

commit sha 5226a6a892f922ea672e5775c61776830aaf27b7

Change the linker's heuristic for computing the entry point for binaries so that shared libraries default to an entry point of 0. * ldlang.c (lang_end): When computing the entry point, only try the start address of the entry section when creating an executable. * ld.texi (Entry point): Update description of heuristic used to choose the entry point. testsuite/ld-alpha/tlspic.rd: Update expected entry point address. testsuite/ld-arm/tls-gdesc-got.d: Likewise. testsuite/ld-i386/tlsnopic.rd: Likewise. testsuite/ld-ia64/tlspic.rd: Likewise. testsuite/ld-sparc/gotop32.rd: Likewise. testsuite/ld-sparc/gotop64.rd: Likewise. testsuite/ld-sparc/tlssunnopic32.rd: Likewise. testsuite/ld-sparc/tlssunnopic64.rd: Likewise. testsuite/ld-sparc/tlssunpic32.rd: Likewise. testsuite/ld-sparc/tlssunpic64.rd: Likewise. testsuite/ld-tic6x/shlib-1.rd: Likewise. testsuite/ld-tic6x/shlib-1b.rd: Likewise. testsuite/ld-tic6x/shlib-1r.rd: Likewise. testsuite/ld-tic6x/shlib-1rb.rd: Likewise. testsuite/ld-tic6x/shlib-noindex.rd: Likewise. testsuite/ld-x86-64/pr14207.d: Likewise. testsuite/ld-x86-64/tlsdesc.rd: Likewise. testsuite/ld-x86-64/tlspic.rd: Likewise. testsuite/ld-x86-64/tlspic2.rd: Likewise.

view details

push time in 3 hours

push eventahjragaas/binutils-gdb

Nick Clifton

commit sha 5226a6a892f922ea672e5775c61776830aaf27b7

Change the linker's heuristic for computing the entry point for binaries so that shared libraries default to an entry point of 0. * ldlang.c (lang_end): When computing the entry point, only try the start address of the entry section when creating an executable. * ld.texi (Entry point): Update description of heuristic used to choose the entry point. testsuite/ld-alpha/tlspic.rd: Update expected entry point address. testsuite/ld-arm/tls-gdesc-got.d: Likewise. testsuite/ld-i386/tlsnopic.rd: Likewise. testsuite/ld-ia64/tlspic.rd: Likewise. testsuite/ld-sparc/gotop32.rd: Likewise. testsuite/ld-sparc/gotop64.rd: Likewise. testsuite/ld-sparc/tlssunnopic32.rd: Likewise. testsuite/ld-sparc/tlssunnopic64.rd: Likewise. testsuite/ld-sparc/tlssunpic32.rd: Likewise. testsuite/ld-sparc/tlssunpic64.rd: Likewise. testsuite/ld-tic6x/shlib-1.rd: Likewise. testsuite/ld-tic6x/shlib-1b.rd: Likewise. testsuite/ld-tic6x/shlib-1r.rd: Likewise. testsuite/ld-tic6x/shlib-1rb.rd: Likewise. testsuite/ld-tic6x/shlib-noindex.rd: Likewise. testsuite/ld-x86-64/pr14207.d: Likewise. testsuite/ld-x86-64/tlsdesc.rd: Likewise. testsuite/ld-x86-64/tlspic.rd: Likewise. testsuite/ld-x86-64/tlspic2.rd: Likewise.

view details

push time in 3 hours

create barnchahjragaas/nano

branch : at-Debian-bullseye

created branch time in 3 hours

delete branch ahjragaas/nano

delete branch : for-Debian-bullseye

delete time in 3 hours

push eventahjragaas/glibc

Adhemerval Zanella

commit sha 5ad589d63bc2d9b1fc3d9f32144acaebb85e0803

support: Add support_open_dev_null_range It returns a range of file descriptor referring to the '/dev/null' pathname. The function takes care of restarting the open range if a file descriptor is found within the specified range and also increases RLIMIT_NOFILE if required. Checked on x86_64-linux-gnu. (cherry picked from commit e814f4b04ee413a7bb3dfa43e74c8fb4abf58359)

view details

Adhemerval Zanella

commit sha 772e33411bc730f832f415f93eb3e7c67e4d5488

Use support_open_dev_null_range io/tst-closefrom, misc/tst-close_range, and posix/tst-spawn5 (BZ #28260) It ensures a continuous range of file descriptor and avoid hitting the RLIMIT_NOFILE. Checked on x86_64-linux-gnu. (cherry picked from commit 6b20880b22d1d0fce7e9f506baa6fe2d5c7fcfdc)

view details

push time in 5 hours

push eventsaagarjha/binutils-gdb

Tom de Vries

commit sha 5335ab68727bbce11c452e3b6bcbfc1ed32f65fd

[gdb/testsuite] Handle supports_memtag in gdb.base/gdb-caching-proc.exp In test-case gdb.base/gdb-caching-proc.exp, we run all procs declared with gdb_caching_proc. Some of these require a gdb instance, some not. We could just do a clean_restart every time, but that would amount to 44 gdb restarts. We try to minimize this by doing this only for the few procs that need it, and hardcoding those in the test-case. For those procs, we do a clean_restart, execute the proc, and then do a gdb_exit, to make sure the gdb instance doesn't linger such that we detect procs that need a gdb instance but are not listed in the test-case. However, that doesn't work in the case of gnat_runtime_has_debug_info. This proc doesn't require a gdb instance because it starts its own. But it doesn't clean up the gdb instance, and since it's not listed, the test-case doesn't clean up the gdb instance eiter. Consequently, the proc supports_memtag (which should be listed, but isn't) uses the gdb instance started by gnat_runtime_has_debug_info rather than throwing an error. Well, unless gnat_runtime_has_debug_info fails before starting a gdb instance, in which case we do run into the error. Fix this by: - doing gdb_exit unconditionally - fixing the resulting error by adding supports_memtag in the test-case to the "needing gdb instance" list Tested on x86_64-linux.

view details

push time in 5 hours

push eventahjragaas/binutils-gdb

Tom de Vries

commit sha 5335ab68727bbce11c452e3b6bcbfc1ed32f65fd

[gdb/testsuite] Handle supports_memtag in gdb.base/gdb-caching-proc.exp In test-case gdb.base/gdb-caching-proc.exp, we run all procs declared with gdb_caching_proc. Some of these require a gdb instance, some not. We could just do a clean_restart every time, but that would amount to 44 gdb restarts. We try to minimize this by doing this only for the few procs that need it, and hardcoding those in the test-case. For those procs, we do a clean_restart, execute the proc, and then do a gdb_exit, to make sure the gdb instance doesn't linger such that we detect procs that need a gdb instance but are not listed in the test-case. However, that doesn't work in the case of gnat_runtime_has_debug_info. This proc doesn't require a gdb instance because it starts its own. But it doesn't clean up the gdb instance, and since it's not listed, the test-case doesn't clean up the gdb instance eiter. Consequently, the proc supports_memtag (which should be listed, but isn't) uses the gdb instance started by gnat_runtime_has_debug_info rather than throwing an error. Well, unless gnat_runtime_has_debug_info fails before starting a gdb instance, in which case we do run into the error. Fix this by: - doing gdb_exit unconditionally - fixing the resulting error by adding supports_memtag in the test-case to the "needing gdb instance" list Tested on x86_64-linux.

view details

push time in 5 hours

push eventsaagarjha/binutils-gdb

Felix Willgerodt

commit sha be24dba6f149d78720fbad2b7133f3865f7b12e5

gdb, doc: Add ieee_half and bfloat16 to list of predefined target types. For some reason these two weren't added to the list when they were orginally added to GDB. gdb/doc/ChangeLog: 2021-09-21 Felix Willgerodt <felix.willgerodt@intel.com> * gdb.texinfo (Predefined Target Types): Mention ieee_half and bfloat16.

view details

push time in 7 hours

push eventahjragaas/binutils-gdb

Felix Willgerodt

commit sha be24dba6f149d78720fbad2b7133f3865f7b12e5

gdb, doc: Add ieee_half and bfloat16 to list of predefined target types. For some reason these two weren't added to the list when they were orginally added to GDB. gdb/doc/ChangeLog: 2021-09-21 Felix Willgerodt <felix.willgerodt@intel.com> * gdb.texinfo (Predefined Target Types): Mention ieee_half and bfloat16.

view details

push time in 7 hours

push eventahjragaas/glibc

Florian Weimer

commit sha 8b8a1d0b7375c547ae905917a03743ed6759c5bc

nptl: Fix type of pthread_mutexattr_getrobust_np, pthread_mutexattr_setrobust_np (bug 28036) Reviewed-by: Carlos O'Donell <carlos@redhat.com> Tested-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit f3e664563361dc17530113b3205998d1f19dc4d9)

view details

push time in 10 hours

push eventahjragaas/glibc

Florian Weimer

commit sha f3e664563361dc17530113b3205998d1f19dc4d9

nptl: Fix type of pthread_mutexattr_getrobust_np, pthread_mutexattr_setrobust_np (bug 28036) Reviewed-by: Carlos O'Donell <carlos@redhat.com> Tested-by: Carlos O'Donell <carlos@redhat.com>

view details

push time in 10 hours

push eventahjragaas/glibc

Aurelien Jarno

commit sha e07504674324fd2fea2fab7d30277725b2b0fe3b

Add NEWS entry for CVE-2020-1751 (bug 25423) Reviewed-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit 07d16a6debc830ebcf9533da5396edd2eff688e0)

view details

Joseph Myers

commit sha 59420258afaf73dc8fab63ce186bac792613fe08

Avoid ldbl-96 stack corruption from range reduction of pseudo-zero (bug 25487). Bug 25487 reports stack corruption in ldbl-96 sinl on a pseudo-zero argument (an representation where all the significand bits, including the explicit high bit, are zero, but the exponent is not zero, which is not a valid representation for the long double type). Although this is not a valid long double representation, existing practice in this area (see bug 4586, originally marked invalid but subsequently fixed) is that we still seek to avoid invalid memory accesses as a result, in case of programs that treat arbitrary binary data as long double representations, although the invalid representations of the ldbl-96 format do not need to be consistently handled the same as any particular valid representation. This patch makes the range reduction detect pseudo-zero and unnormal representations that would otherwise go to __kernel_rem_pio2, and returns a NaN for them instead of continuing with the range reduction process. (Pseudo-zero and unnormal representations whose unbiased exponent is less than -1 have already been safely returned from the function before this point without going through the rest of range reduction.) Pseudo-zero representations would previously result in the value passed to __kernel_rem_pio2 being all-zero, which is definitely unsafe; unnormal representations would previously result in a value passed whose high bit is zero, which might well be unsafe since that is not a form of input expected by __kernel_rem_pio2. Tested for x86_64. (cherry picked from commit 9333498794cde1d5cca518badf79533a24114b6f)

view details

Florian Weimer

commit sha 4b8628acab03a4875a5c3bfe847c9f0a1ccbd081

math/test-sinl-pseudo: Use stack protector only if available This fixes commit 9333498794cde1d5cca518bad ("Avoid ldbl-96 stack corruption from range reduction of pseudo-zero (bug 25487)."). (cherry picked from commit c10acd40262486dac597001aecc20ad9d3bd0e4a)

view details

Aurelien Jarno

commit sha 477587c75e04ed86e65c711f932e2703bdea0693

Add NEWS entry for CVE-2020-10029 (bug 25487) (cherry picked from commit 15ab195229dc288d1d49612c3de14a33b88065ed)

view details

Andreas Schwab

commit sha 8b84316420dbca05853c5a7176255b635e4a223e

Fix iconv buffer handling with IGNORE error handler (bug #18830) (cherry picked from commit 4802be92c891903caaf8cae47f685da6f26d4b9a)

view details

Florian Weimer

commit sha 711f183508886b03585633cffab3b37869d8f35f

support: Implement TEST_COMPARE_STRING (cherry picked from commit 1df872fd74f730bcae3df201a229195445d2e18a)

view details

Adhemerval Zanella

commit sha 62df32d604fb95243b0eaf1db8a8ef00d060ea1e

support: Fix printf format for TEST_COMPARE_STRING Fix the following on 32 bits targets: support_test_compare_string.c: In function 'support_test_compare_string': support_test_compare_string.c:80:37: error: format '%lu' expects argument of type 'long unsigned int', but argument 2 has type 'size_t' {aka 'unsigned int'} [-Werror=format=] printf (" string length: %lu bytes\n", left_length); ~~^ ~~~~~~~~~~~ %u Checked on arm-linux-gnueabihf. * support/support_test_compare_string.c (support_test_compare_string): Fix printf format. (cherry picked from commit 00c86a37d1b63044e3169d1f2ebec23447c73f79)

view details

Florian Weimer

commit sha 222b1517cd86e5a3eadcfd7787f757fdb76db11b

support: Correct error message for TEST_COMPARE_STRING It should say "string", not "blob". (cherry picked from commit 6175507c06de56e03407004bd2f289ed2cce034d)

view details

Arjun Shankar

commit sha 68d583bb1cc355ad636f4066f5dee39b317c106c

Add Transliterations for Unicode Misc. Mathematical Symbols-A/B [BZ #23132] This commit adds previously missing transliterations for several code points in the Unicode blocks "Miscellaneous Mathematical Symbols-A/B" - transliterated to their approximate ASCII representations. It also adds a corresponding iconv transliteration test. Reviewed-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit 513aaa0d782f8fae36732d06ca59d658149f0139)

view details

Arjun Shankar

commit sha bdaa594506063a760cf0308a8db2d2524c51839e

support: Add xsetlocale function (cherry picked from commit cce35a50c1de0cec5cd1f6c18979ff6ee3ea1dd1)

view details

Arjun Shankar

commit sha ec51be40c787782ceac65a33dc163c8b61bc54d1

Rewrite iconv option parsing [BZ #19519] This commit replaces string manipulation during `iconv_open' and iconv_prog option parsing with a structured, flag based conversion specification. In doing so, it alters the internal `__gconv_open' interface and accordingly adjusts its uses. This change fixes several hangs in the iconv program and therefore includes a new test to exercise iconv_prog options that originally led to these hangs. It also includes a new regression test for option handling in the iconv function. Reviewed-by: Florian Weimer <fweimer@redhat.com> Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org> Reviewed-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit 91927b7c76437db860cd86a7714476b56bb39d07)

view details

Aurelien Jarno

commit sha 8fb94f88249508cdc9addd01ca6124d3d8b94d69

Add NEWS entry for CVE-2016-10228 (bug 19519) (cherry picked from commit 17a0126abf02955cabf6256c67f8f9462a64163f)

view details

Arjun Shankar

commit sha 670c675da3f7b8b2575781309a6c0753df0bd191

intl: Handle translation output codesets with suffixes [BZ #26383] Commit 91927b7c7643 (Rewrite iconv option parsing [BZ #19519]) did not handle cases where the output codeset for translations (via the `gettext' family of functions) might have a caller specified encoding suffix such as TRANSLIT or IGNORE. This led to a regression where translations did not work when the codeset had a suffix. This commit fixes the above issue by parsing any suffixes passed to __dcigettext and adds two new test-cases to intl/tst-codeset.c to verify correct behaviour. The iconv-internal function __gconv_create_spec and the static iconv-internal function gconv_destroy_spec are now visible internally within glibc and used in intl/dcigettext.c. (cherry picked from commit 7d4ec75e111291851620c6aa2c4460647b7fd50d)

view details

Arjun Shankar

commit sha d8ae6c00a945aadc971cf2c33d9fb0ed31ebb5df

iconv: Accept redundant shift sequences in IBM1364 [BZ #26224] The IBM1364, IBM1371, IBM1388, IBM1390 and IBM1399 character sets share converter logic (iconvdata/ibm1364.c) which would reject redundant shift sequences when processing input in these character sets. This led to a hang in the iconv program (CVE-2020-27618). This commit adjusts the converter to ignore redundant shift sequences and adds test cases for iconv_prog hangs that would be triggered upon their rejection. This brings the implementation in line with other converters that also ignore redundant shift sequences (e.g. IBM930 etc., fixed in commit 692de4b3960d). Reviewed-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit 9a99c682144bdbd40792ebf822fe9264e0376fb5)

view details

Michael Colavita

commit sha 5fa7884e25c5d11718253244fd1bc570c60f4cc8

iconv: Fix incorrect UCS4 inner loop bounds (BZ#26923) Previously, in UCS4 conversion routines we limit the number of characters we examine to the minimum of the number of characters in the input and the number of characters in the output. This is not the correct behavior when __GCONV_IGNORE_ERRORS is set, as we do not consume an output character when we skip a code unit. Instead, track the input and output pointers and terminate the loop when either reaches its limit. This resolves assertion failures when resetting the input buffer in a step of iconv, which assumes that the input will be fully consumed given sufficient output space. (cherry picked from commit 228edd356f03bf62dcf2b1335f25d43c602ee68d)

view details

Siddhesh Poyarekar

commit sha 3668134a9ef34b1a96f6b56666ae04886a99d33f

Add NEWS entry for CVE-2020-29562 (BZ #26923) BZ #26923 now has a CVE entry, so add a NEWS entry for it. (cherry picked from commit 38a9e93cb1c58e3c899d638480e6d6e42af8e6fc)

view details

Florian Weimer

commit sha 2777e19c0550ca6c21f3604fad02084a8130f3a5

nscd: Fix use-after-free in addgetnetgrentX [BZ #23520] addinnetgrX may use the heap-allocated buffer, so free the buffer in this function. (cherry picked from commit 745664bd798ec8fd50438605948eea594179fba1)

view details

DJ Delorie

commit sha c49cbcdc321dd31026955f7f170d0018848b3d2f

nscd: Fix double free in netgroupcache [BZ #27462] In commit 745664bd798ec8fd50438605948eea594179fba1 a use-after-free was fixed, but this led to an occasional double-free. This patch tracks the "live" allocation better. Tested manually by a third party. Related: RHBZ 1927877 Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org> Reviewed-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit dca565886b5e8bd7966e15f0ca42ee5cff686673)

view details

Andreas Schwab

commit sha 73886db6218e613bd6d4edf529f11e008a6c2fa6

wordexp: handle overflow in positional parameter number (bug 28011) Use strtoul instead of atoi so that overflow can be detected. (cherry picked from commit 5adda61f62b77384718b4c0d8336ade8f2b4b35c)

view details

push time in 14 hours

push eventahjragaas/binutils-gdb

GDB Administrator

commit sha 01723a35030c0198c5bac31d8ca6959f7da17e2e

Automatic date update in version.in

view details

push time in 15 hours

push eventahjragaas/binutils-gdb

GDB Administrator

commit sha 27439f0edab99c6870cf7fe042074e47632f3fbd

Automatic date update in version.in

view details

push time in 15 hours

push eventahjragaas/binutils-gdb

GDB Administrator

commit sha c5de623fa363fff127cd8a1292e407764e385ffa

Automatic date update in version.in

view details

push time in 15 hours

push eventsaagarjha/binutils-gdb

GDB Administrator

commit sha 01723a35030c0198c5bac31d8ca6959f7da17e2e

Automatic date update in version.in

view details

push time in 15 hours

push eventsaagarjha/binutils-gdb

Tom de Vries

commit sha 5936ac73edd7d196611a9690a9a99f7137479e79

[gdb/testsuite] Fix gdb.ada/interface.exp with gcc-9 When running test-case gdb.ada/interface.exp with gcc-9, we run into: ... (gdb) info locals^M s = (x => 1, y => 2, w => 3, h => 4)^M r = (x => 1, y => 2, w => 3, h => 4)^M (gdb) FAIL: gdb.ada/interface.exp: info locals ... The failure is caused by the regexp expecting variable r followed by variable s. Fix this by allowing variable s followed by variable r as well. Tested on x86_64-linux.

view details

push time in 16 hours

push eventahjragaas/binutils-gdb

Tom de Vries

commit sha 5936ac73edd7d196611a9690a9a99f7137479e79

[gdb/testsuite] Fix gdb.ada/interface.exp with gcc-9 When running test-case gdb.ada/interface.exp with gcc-9, we run into: ... (gdb) info locals^M s = (x => 1, y => 2, w => 3, h => 4)^M r = (x => 1, y => 2, w => 3, h => 4)^M (gdb) FAIL: gdb.ada/interface.exp: info locals ... The failure is caused by the regexp expecting variable r followed by variable s. Fix this by allowing variable s followed by variable r as well. Tested on x86_64-linux.

view details

push time in 16 hours

push eventsaagarjha/binutils-gdb

Tom de Vries

commit sha c45a683f8f9195bf7cc53bc645a20092c7155629

[gdb] Change register_test to use std::function arg Change register_test to use std::function arg, such that we can do: ... register_test (test_name, [=] () { SELF_CHECK (...); }); ... Tested on x86_64-linux.

view details

Tom de Vries

commit sha ff1c1bb9be3ed77fdabe594d977a9ccc67870fd0

[gdb/testsuite] Register test for each arch separately in register_test_foreach_arch In gdb/disasm-selftests.c we have: ... selftests::register_test_foreach_arch ("print_one_insn", selftests::print_one_insn_test); ... and we get: ... $ gdb -q -batch -ex "maint selftest print_one_insn" 2>&1 \ | grep ^Running Running selftest print_one_insn. $ ... Change the semantics register_test_foreach_arch such that a version of print_one_insn is registered for each architecture, such that we have: ... $ gdb -q -batch -ex "maint selftest print_one_insn" 2>&1 \ | grep ^Running Running selftest print_one_insn::A6. Running selftest print_one_insn::A7. Running selftest print_one_insn::ARC600. ... $ ... This makes it f.i. possible to do: ... $ gdb -q -batch a.out -ex "maint selftest print_one_insn::armv8.1-m.main" Running selftest print_one_insn::armv8.1-m.main. Self test failed: self-test failed at src/gdb/disasm-selftests.c:165 Ran 1 unit tests, 1 failed ... Tested on x86_64-linux with an --enable-targets=all build.

view details

Tom de Vries

commit sha acb7bdf0d2235291adba1049a099729255571f2b

[gdb/testsuite] Fix gdb.ada/mi_prot.exp When running test-case gdb.ada/mi_prot.exp with gcc 8.5.0, we run into: ... (gdb) ^M Expecting: ^(-stack-list-arguments --no-frame-filters 1[^M ]+)?(\^done,stack=.*[^M ]+[(]gdb[)] ^M [ ]*) -stack-list-arguments --no-frame-filters 1^M ^done,stack-args=[frame={level="0",args=[{name="<_object>",value="(ceiling_priority =\ > 97, local => 0)"},{name="v",value="5"},{name="<_objectO>",value="true"}]},frame={le\ vel="1",args=[{name="v",value="5"},{name="<_objectO>",value="true"}]},frame={level="2\ ",args=[]}]^M (gdb) ^M FAIL: gdb.ada/mi_prot.exp: -stack-list-arguments --no-frame-filters 1 (unexpected out\ put) ... Fix this by updating the regexp to expect "^done,stack-args=" instead of "^done,stack=". Tested on x86_64-linux.

view details

push time in 16 hours

push eventahjragaas/binutils-gdb

Tom de Vries

commit sha c45a683f8f9195bf7cc53bc645a20092c7155629

[gdb] Change register_test to use std::function arg Change register_test to use std::function arg, such that we can do: ... register_test (test_name, [=] () { SELF_CHECK (...); }); ... Tested on x86_64-linux.

view details

Tom de Vries

commit sha ff1c1bb9be3ed77fdabe594d977a9ccc67870fd0

[gdb/testsuite] Register test for each arch separately in register_test_foreach_arch In gdb/disasm-selftests.c we have: ... selftests::register_test_foreach_arch ("print_one_insn", selftests::print_one_insn_test); ... and we get: ... $ gdb -q -batch -ex "maint selftest print_one_insn" 2>&1 \ | grep ^Running Running selftest print_one_insn. $ ... Change the semantics register_test_foreach_arch such that a version of print_one_insn is registered for each architecture, such that we have: ... $ gdb -q -batch -ex "maint selftest print_one_insn" 2>&1 \ | grep ^Running Running selftest print_one_insn::A6. Running selftest print_one_insn::A7. Running selftest print_one_insn::ARC600. ... $ ... This makes it f.i. possible to do: ... $ gdb -q -batch a.out -ex "maint selftest print_one_insn::armv8.1-m.main" Running selftest print_one_insn::armv8.1-m.main. Self test failed: self-test failed at src/gdb/disasm-selftests.c:165 Ran 1 unit tests, 1 failed ... Tested on x86_64-linux with an --enable-targets=all build.

view details

Tom de Vries

commit sha acb7bdf0d2235291adba1049a099729255571f2b

[gdb/testsuite] Fix gdb.ada/mi_prot.exp When running test-case gdb.ada/mi_prot.exp with gcc 8.5.0, we run into: ... (gdb) ^M Expecting: ^(-stack-list-arguments --no-frame-filters 1[^M ]+)?(\^done,stack=.*[^M ]+[(]gdb[)] ^M [ ]*) -stack-list-arguments --no-frame-filters 1^M ^done,stack-args=[frame={level="0",args=[{name="<_object>",value="(ceiling_priority =\ > 97, local => 0)"},{name="v",value="5"},{name="<_objectO>",value="true"}]},frame={le\ vel="1",args=[{name="v",value="5"},{name="<_objectO>",value="true"}]},frame={level="2\ ",args=[]}]^M (gdb) ^M FAIL: gdb.ada/mi_prot.exp: -stack-list-arguments --no-frame-filters 1 (unexpected out\ put) ... Fix this by updating the regexp to expect "^done,stack-args=" instead of "^done,stack=". Tested on x86_64-linux.

view details

push time in 16 hours

push eventahjragaas/glibc

Paul A. Clarke

commit sha 064b475a2e5662b6b3973fabf505eade86e61510

powerpc: Fix unrecognized instruction errors with recent GCC Recent binutils commit b25f942e18d6ecd7ec3e2d2e9930eb4f996c258a changes the behavior of `.machine` directives to override, rather than augment, the base CPU. This can result in _reduced_ functionality when, for example, compiling for default machine "power8", but explicitly asking for ".machine power5", which loses Altivec instructions. In tst-ucontext-ppc64-vscr.c, while the instructions provoking the new error messages are bracketed by ".machine power5", which is ostensibly Power ISA 2.03 (POWER5), the POWER5 processor did not support the VSX subset, so these instructions are not recognized as "power5". Error: unrecognized opcode: `vspltisb' Error: unrecognized opcode: `vpkuwus' Error: unrecognized opcode: `mfvscr' Error: unrecognized opcode: `stvx' Manually adding the VSX subset via ".machine altivec" is sufficient. Reviewed-by: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>

view details

push time in 17 hours

push eventahjragaas/binutils-gdb

Matthew Malcomson

commit sha dbd880c7c11191db9690f0dc26f42e4e3e2a9a40

morello-binutils: Adjust c64_valid_cap_range calculation This function had a buggy implementation of rounding a value up to a given power of 2. Aligning to a multiple of 16 would align to a multiple of 32 and so on. This was observable when linking object files that had very large objects in them. The compiler would ensure that these objects are large enough that they are exactly representable, but the linker would complain that they are not because the linker asserted extra alignment than the compiler. Here we fix the bug, add a few testcases, and adjust an existing testcase in the area.

view details

push time in a day

push eventahjragaas/bash

Chet Ramey

commit sha 232f5919645d0a02004a94a3ee8e28a550165df9

more updates for autoconf-2.71: removing usage of AC_TRY_COMPILE

view details

push time in a day

push eventahjragaas/glibc

Florian Weimer

commit sha 73c7f5a87971de2797f261e1a447f68dce09284b

nptl: pthread_kill needs to return ESRCH for old programs (bug 19193) The fix for bug 19193 breaks some old applications which appear to use pthread_kill to probe if a thread is still running, something that is not supported by POSIX. (cherry picked from commit 95dba35bf05e4a5d69dfae5e9c9d4df3646a7f93)

view details

push time in a day

push eventahjragaas/glibc

Florian Weimer

commit sha 7e84ac3a3ac9e7c4dc10de2ce65db971b9650e4d

elf: Include <sysdep.h> in elf/dl-debug-symbols.S This is necessary to generate assembler marker sections on some targets. Reviewed-by: Szabolcs Nagy <szabolcs.nagy@arm.com>

view details

push time in a day

push eventsaagarjha/binutils-gdb

Tom de Vries

commit sha 6f265beb28a7465c9e75fdb169d15a87f9a3a5d6

[gdb/testsuite] Fix gdb.ada/big_packed_array.exp xfail for -m32 With test-case gdb.ada/big_packed_array.exp and target board unix/-m32 I run into: ... (gdb) print bad^M $2 = (0 => 0 <repeats 24 times>, 160)^M (gdb) FAIL: gdb.ada/big_packed_array.exp: scenario=minimal: print bad ... The problem is that while the variable is an array of 196 bits (== 24.5 bytes), the debug information describes it as 25 unsigned char. This is PR gcc/101643, and the test-case contains an xfail for this, which catches only: ... (gdb) print bad^M $2 = (0 => 0 <repeats 25 times>)^M ... Fix this by updating the xfail pattern. Tested on x86_64-linux.

view details

push time in a day

push eventahjragaas/binutils-gdb

Tom de Vries

commit sha 6f265beb28a7465c9e75fdb169d15a87f9a3a5d6

[gdb/testsuite] Fix gdb.ada/big_packed_array.exp xfail for -m32 With test-case gdb.ada/big_packed_array.exp and target board unix/-m32 I run into: ... (gdb) print bad^M $2 = (0 => 0 <repeats 24 times>, 160)^M (gdb) FAIL: gdb.ada/big_packed_array.exp: scenario=minimal: print bad ... The problem is that while the variable is an array of 196 bits (== 24.5 bytes), the debug information describes it as 25 unsigned char. This is PR gcc/101643, and the test-case contains an xfail for this, which catches only: ... (gdb) print bad^M $2 = (0 => 0 <repeats 25 times>)^M ... Fix this by updating the xfail pattern. Tested on x86_64-linux.

view details

push time in a day

push eventahjragaas/glibc

Florian Weimer

commit sha 95dba35bf05e4a5d69dfae5e9c9d4df3646a7f93

nptl: pthread_kill needs to return ESRCH for old programs (bug 19193) The fix for bug 19193 breaks some old applications which appear to use pthread_kill to probe if a thread is still running, something that is not supported by POSIX.

view details

push time in a day

push eventahjragaas/binutils-gdb

Simon Marchi

commit sha 56d9e3c5623d9ebaffb4532a503e67203e4d5488

gdbsupport/gdb_proc_service.h: use decltype instead of typeof Bug 28341 shows that GDB fails to compile when built with -std=c++11. I don't know much about the use case, but according to the author of the bug: I encountered the scenario where CXX is set to "g++ -std=c++11" when I try to compile binutils under GCC as part of the GCC 3-stage compilation, which is common for building a cross-compiler. The author of the bug suggests using __typeof__ instead of typeof. But since we're using C++, we might as well use decltype, which is standard. This is what this patch does. The failure (and fix) can be observed by configuring GDB with CXX="g++ -std=c++11": CXX linux-low.o In file included from /home/simark/src/binutils-gdb/gdbserver/gdb_proc_service.h:22, from /home/simark/src/binutils-gdb/gdbserver/linux-low.h:27, from /home/simark/src/binutils-gdb/gdbserver/linux-low.cc:20: /home/simark/src/binutils-gdb/gdbserver/../gdbsupport/gdb_proc_service.h:177:50: error: expected constructor, destructor, or type conversion before (token 177 | __attribute__((visibility ("default"))) typeof (SYM) SYM | ^ /home/simark/src/binutils-gdb/gdbserver/../gdbsupport/gdb_proc_service.h:179:1: note: in expansion of macro PS_EXPORT 179 | PS_EXPORT (ps_get_thread_area); | ^~~~~~~~~ Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=28341 Change-Id: I84fbaae938209d8d935ca08dec9b7e6a0dd1bda0

view details

push time in a day