{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":24849687,"defaultBranch":"master","name":"gdb","ownerLogin":"bsdjhb","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2014-10-06T14:39:41.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/8976613?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1722875979.0","currentOid":""},"activityList":{"items":[{"before":null,"after":"c59311529fbed8adea5e49ad6642a9beb8909411","ref":"refs/heads/kgdb-15","pushedAt":"2024-08-05T16:39:39.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"Chase #includes","shortMessageHtmlLink":"Chase #includes"}},{"before":"9dd918142787246ea7ed53494d9cbc6b51486133","after":"6ce1ea97af20b9e618c524aa719e70c17dacda74","ref":"refs/heads/master","pushedAt":"2024-08-02T19:07:51.000Z","pushType":"push","commitsCount":1095,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"gdb,testsuite: fix gdb.base/list-dot-nodebug and make it more robust\n\nThiago Jung Bauermann noticed that gdb.base/list-dot-nodebug was not\nactually compiling the test with some debuginfo in the relevant part,\nand while fixing I noticed that the base assumption of the \"some\" case\nwas wrong, GDB would select some symtab as a default location and the\ntest would always fail. This fix makes printing the default location\nonly be tested when there is no debuginfo.\n\nWhen testing with no debuginfo, if a system had static libc debuginfo,\nthe test would also fail. To add an extra layer of robustness to the\ntest, this rewrite also strips any stray debuginfo from the executable.\nThe test would only fail now if it runs in a system that can't handle\nstripped debuginfo and has static debuginfo pre-installed.\n\nReported-By: Tom de Vries <tdevries@suse.de>\nReported-By: Thiago Jung Bauermann <thiago.bauermann@linaro.org>\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id=31721\nReviewed-by: Thiago Jung Bauermann <thiago.bauermann@linaro.org>\nApproved-By: Andrew Burgess <aburgess@redhat.com>","shortMessageHtmlLink":"gdb,testsuite: fix gdb.base/list-dot-nodebug and make it more robust"}},{"before":"e8cd90f039c33726af3441ccf56eea7b69ed0de1","after":"9dd918142787246ea7ed53494d9cbc6b51486133","ref":"refs/heads/master","pushedAt":"2024-04-15T17:39:32.000Z","pushType":"push","commitsCount":43,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"Remove dependency upon shlwapi library when building BFD for Windows/MinGW environments.\n\n  PR 31527","shortMessageHtmlLink":"Remove dependency upon shlwapi library when building BFD for Windows/…"}},{"before":"467a34bb9e61dfaddf7209e04455a21600b6ef5f","after":"e8cd90f039c33726af3441ccf56eea7b69ed0de1","ref":"refs/heads/master","pushedAt":"2024-04-09T17:22:01.000Z","pushType":"push","commitsCount":195,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"Rewrite gdb_bfd_error_handler\n\nThis patch rewrites gdb_bfd_error_handler to use 'bfd_print_error' to\ngenerate the text of the warning, and then emits it using 'warning'.\nThe current code in the tree is a bit wrong because it may do the\nwrong thing when BFD uses ones of its printf extensions.\n\nThis also adds locking to increment_bfd_error_count.  This is\nimportant now that some BFD operations can be done on worker threads.\n\nThis approach makes it simpler for worker threads to intercept any\nmessages.\n\nRegression tested on x86-64 Fedora 38.","shortMessageHtmlLink":"Rewrite gdb_bfd_error_handler"}},{"before":"870ab3d385bf5041780d76e46a5d800c1faf59ed","after":"467a34bb9e61dfaddf7209e04455a21600b6ef5f","ref":"refs/heads/thread_test_fixes","pushedAt":"2024-03-23T00:30:30.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"gdb tests: Allow for \"LWP\" or \"process\" in thread IDs from info threads\n\nSeveral tests assume that the first word after a thread ID in 'info\nthreads' output is \"Thread\".  However, several targets use \"LWP\"\ninstead such as the FreeBSD and NetBSD native targets.  The Linux\nnative target also uses \"LWP\" if libthread_db is not being used.\nTargets that do not support threads use \"process\" as the first word\nvia normal_pid_to_str.\n\nAdd a tdlabel_re global variable as a regular-expression for a thread\nlabel in `info threads' that matches either \"process\", \"Thread\", or\n\"LWP\".\n\nSome other tests in the tree don't require a specific word, and\nsome targets may use other first words (e.g. OpenBSD uses \"thread\"\nand Ravenscar threads use \"Ravenscar Thread\").","shortMessageHtmlLink":"gdb tests: Allow for \"LWP\" or \"process\" in thread IDs from info threads"}},{"before":"e9315f148d56b3f4c7cfeef469633e85933d412c","after":"467a34bb9e61dfaddf7209e04455a21600b6ef5f","ref":"refs/heads/master","pushedAt":"2024-03-23T00:30:17.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"gdb tests: Allow for \"LWP\" or \"process\" in thread IDs from info threads\n\nSeveral tests assume that the first word after a thread ID in 'info\nthreads' output is \"Thread\".  However, several targets use \"LWP\"\ninstead such as the FreeBSD and NetBSD native targets.  The Linux\nnative target also uses \"LWP\" if libthread_db is not being used.\nTargets that do not support threads use \"process\" as the first word\nvia normal_pid_to_str.\n\nAdd a tdlabel_re global variable as a regular-expression for a thread\nlabel in `info threads' that matches either \"process\", \"Thread\", or\n\"LWP\".\n\nSome other tests in the tree don't require a specific word, and\nsome targets may use other first words (e.g. OpenBSD uses \"thread\"\nand Ravenscar threads use \"Ravenscar Thread\").","shortMessageHtmlLink":"gdb tests: Allow for \"LWP\" or \"process\" in thread IDs from info threads"}},{"before":"12d5d5bfd0201711ac3b14d8cd92589919a82b7a","after":"e9315f148d56b3f4c7cfeef469633e85933d412c","ref":"refs/heads/master","pushedAt":"2024-03-22T23:36:36.000Z","pushType":"push","commitsCount":40,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"windows-nat: Use gdb_realpath\n\nUse gdb_realpath instead of realpath in windows-nat.c:windows_make_so,\nso that we don't have to manually call free.\n\nApproved-By: John Baldwin <jhb@FreeBSD.org>\nChange-Id: Id3cda7e177ac984c9a5f7c23f354e72bd561edff","shortMessageHtmlLink":"windows-nat: Use gdb_realpath"}},{"before":"000f48f5d95e0d78f48670a8da6661601e15297a","after":"870ab3d385bf5041780d76e46a5d800c1faf59ed","ref":"refs/heads/thread_test_fixes","pushedAt":"2024-03-19T22:41:47.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"gdb tests: Allow for \"LWP\" in thread IDs from info threads.\n\nSeveral tests assume that the first word after a thread ID in 'info\nthreads' output is \"Thread\".  However, several targets use \"LWP\"\ninstead such as the FreeBSD and NetBSD native targets.  The Linux\nnative target also uses \"LWP\" if libthread_db is not being used.\nTargets that do not support threads use \"process\" as the first word\nvia normal_pid_to_str.\n\nAdd a tdlabel_re global variable as a regular-expression for a thread\nlabel in `info threads' that matches either \"process\", \"Thread\", or\n\"LWP\".\n\nSome other tests in the tree don't require a specific word, and\nsome targets may use other first words (e.g. OpenBSD uses \"thread\"\nand Ravenscar threads use \"Ravenscar Thread\").","shortMessageHtmlLink":"gdb tests: Allow for \"LWP\" in thread IDs from info threads."}},{"before":"cf16ab724a41e4cbaf723b5633d4e7b29f61372b","after":"12d5d5bfd0201711ac3b14d8cd92589919a82b7a","ref":"refs/heads/master","pushedAt":"2024-03-19T16:08:57.000Z","pushType":"push","commitsCount":51,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"Fix two serious flake8 reports\n\nflake8 points out that some code in frame_filters.py is referring to\nundefined variables.\n\nIn the first hunk, I've changed the code to match what other\n'complete' methods do in this file.\n\nIn the second hunk, I've simply removed the try/except -- if\nget_filter_priority fails, it will raise GdbError, which is already\nhandled properly by gdb.","shortMessageHtmlLink":"Fix two serious flake8 reports"}},{"before":"b081c003ff88bc14f238f53a12e7c3fb26f0cd35","after":"cf16ab724a41e4cbaf723b5633d4e7b29f61372b","ref":"refs/heads/master","pushedAt":"2024-03-12T19:11:17.000Z","pushType":"push","commitsCount":108,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"[gdb/tdep] Fix gdb.base/watch-bitfields.exp on aarch64\n\nOn aarch64-linux, with test-case gdb.base/watch-bitfields.exp I run into:\n...\n(gdb) continue^M\nContinuing.^M\n^M\nHardware watchpoint 2: -location q.a^M\n^M\nOld value = 1^M\nNew value = 0^M\nmain () at watch-bitfields.c:42^M\n42        q.h--;^M\n(gdb) FAIL: $exp: -location watch against bitfields: q.e: 0->5: continue\n...\n\nIn a minimal form, if we step past line 37 which sets q.e, and we have a\nwatchpoint set on q.e, it triggers:\n...\n$ gdb -q -batch watch-bitfields -ex \"b 37\" -ex run -ex \"watch q.e\" -ex step\nBreakpoint 1 at 0x410204: file watch-bitfields.c, line 37.\n\nBreakpoint 1, main () at watch-bitfields.c:37\n37        q.e = 5;\nHardware watchpoint 2: q.e\n\nHardware watchpoint 2: q.e\n\nOld value = 0\nNew value = 5\nmain () at /home/vries/gdb/src/gdb/testsuite/gdb.base/watch-bitfields.c:38\n38        q.f = 6;\n...\n\nHowever, if we set in addition a watchpoint on q.a, the watchpoint on q.e\ndoesn't trigger.\n\nHow does this happen?\n\nBitfield q.a is just bit 0 of byte 0, and bitfield q.e is bit 4..7 of byte 1\nand bit 1 of byte 2.  So, watch q.a should watch byte 0, and watch q.e should\nwatch bytes 1 and 2.\n\nUsing \"maint set show-debug-regs on\" (and some more detailed debug prints) we\nget:\n...\nWP2: addr=0x440028 (orig=0x440029), ctrl=0x000000d5, ref.count=1\n  ctrl: enabled=1, offset=1, len=2\nWP3: addr=0x440028 (orig=0x440028), ctrl=0x00000035, ref.count=1\n  ctrl: enabled=1, offset=0, len=1\n...\nwhich matches that.\n\nWhen executing line 37, a hardware watchpoint trap triggers and we hit\naarch64_stopped_data_address with addr_trap == 0x440028:\n...\n(gdb) p /x addr_trap\n$1 = 0x440028\n....\nand since the loop in aarch64_stopped_data_address walks backward, we check\nWP3 first, which matches, and consequently target_stopped_by_watchpoint\nreturns true in watchpoints_triggered.\n\nLikewise for target_stopped_data_address, which also returns addr == 0x440028.\nWatchpoints_triggered matches watchpoint q.a to that address, and sets\nwatch_triggered_yes.\n\nHowever, subsequently the value of q.a is checked, and it's the same value as\nbefore (becase the insn in line 37 didn't change q.a), so the watchpoint\nhardware trap is not reported to the user.\n\nThe problem originates from that fact that aarch64_stopped_data_address picked\nWP3 instead of WP2.\n\nThere's something we can do about this.  In the example above, both\ntarget_stopped_by_watchpoint and target_stopped_data_address returned true.\nInstead we can return true in target_stopped_by_watchpoint but false in\ntarget_stopped_data_address.  This lets watchpoints_triggered known that a\nwatchpoint was triggered, but we don't know where, and both watchpoints\nget set to watch_triggered_unknown.\n\nSubsequently, the values of both q.a and q.e are checked, and since q.e is not\nthe same value as before, the watchpoint hardware trap is reported to the user.\n\nNote that this works well for regular (write) watchpoints (watch command), but\nnot for read watchpoints (rwatch command), because for those no value is\nchecked.  Likewise for access watchpoints (awatch command).\n\nSo, fix this by:\n- passing a nullptr in aarch64_fbsd_nat_target::stopped_by_watchpoint and\n  aarch64_linux_nat_target::stopped_by_watchpoint to make clear we're not\n  interested in the stop address,\n- introducing a two-phase approach in aarch64_stopped_data_address, where:\n  - phase one handles access and read watchpoints, as before, and\n  - phase two handles write watchpoints, where multiple matches cause:\n    - return true if addr_p == null, and\n    - return false if addr_p != null.\n\nTested on aarch64-linux.\n\nApproved-By: Luis Machado <luis.machado@arm.com>\n\nPR tdep/31214\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id=31214","shortMessageHtmlLink":"[gdb/tdep] Fix gdb.base/watch-bitfields.exp on aarch64"}},{"before":"407ca654547b100903f7eab44d078a2440736f13","after":"b081c003ff88bc14f238f53a12e7c3fb26f0cd35","ref":"refs/heads/master","pushedAt":"2024-02-29T00:04:15.000Z","pushType":"push","commitsCount":7,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"aarch64: Use aarch64_debug_printf in a few more places\n\nNo functional change\n\nApproved-By: Simon Marchi <simon.marchi@efficios.com>","shortMessageHtmlLink":"aarch64: Use aarch64_debug_printf in a few more places"}},{"before":"66637e209cc836c19a21a28e91046649c7702037","after":"407ca654547b100903f7eab44d078a2440736f13","ref":"refs/heads/master","pushedAt":"2024-02-27T22:02:49.000Z","pushType":"push","commitsCount":1176,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"Two minor addrmap cleanups\n\nWhile working on a different patch, I found a couple of simple addrmap\ncleanups.\n\nIn one case, a forward declaration is no longer needed, as the header\nnow includes addrmap.h.\n\nIn the other, an include of addrmap.h is no longer needed.\n\nTested by rebuilding.","shortMessageHtmlLink":"Two minor addrmap cleanups"}},{"before":null,"after":"70d0d9f04a51b8c441334f42cd5dfb1f9215be53","ref":"refs/heads/users/ARM/morello-binutils-gdb-master","pushedAt":"2023-12-30T00:06:31.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"morello, testsuite: Fix up morello-stubs-static.d\n\nThe expected disassembly for this test is testing for the wrong thing: it\nexpects the adrp immediate to be zero-extended instead of sign-extended, which\nis incorrect.  That shows up as a test failure after fixing the disassembly in\nthe previous patch.  This patch fixes the test.","shortMessageHtmlLink":"morello, testsuite: Fix up morello-stubs-static.d"}},{"before":"97b29a61f7f001550fe985bf2deea1550e3c20dd","after":"66637e209cc836c19a21a28e91046649c7702037","ref":"refs/heads/master","pushedAt":"2023-12-20T22:06:44.000Z","pushType":"push","commitsCount":66,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"i386: Use a fallback XSAVE layout for remote targets\n\nIf a target provides a target description including registers from the\nXSAVE extended region, but does not provide an XSAVE layout, use a\nfallback XSAVE layout based on the included registers.  This fallback\nlayout matches GDB's behavior in earlier releases which assumes the\nlayout from Intel CPUs.\n\nThis fallback layout is currently only used for remote targets since\nnative targets which support XSAVE provide an explicit layout derived\nfrom CPUID.\n\nPR gdb/30912\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id=30912\nApproved-By: Simon Marchi <simon.marchi@efficios.com>","shortMessageHtmlLink":"i386: Use a fallback XSAVE layout for remote targets"}},{"before":null,"after":"eb8f4e60698bbed89a98c9bc23fbc520140e030a","ref":"refs/heads/kgdb-14","pushedAt":"2023-12-13T19:27:59.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"Cleanups to kgdb-main.c","shortMessageHtmlLink":"Cleanups to kgdb-main.c"}},{"before":"a43494a9edbe1f773d2ba289e371bb45a0a06ae4","after":"003d50876f9882820e915fa34542425584e68814","ref":"refs/heads/kgdb-13","pushedAt":"2023-12-13T16:46:28.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"Whitespace fix.","shortMessageHtmlLink":"Whitespace fix."}},{"before":"d9eb7e9563b49d36448a94177333640c4e534fd6","after":"66637e209cc836c19a21a28e91046649c7702037","ref":"refs/heads/xsave_fallback","pushedAt":"2023-11-27T21:54:24.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"i386: Use a fallback XSAVE layout for remote targets\n\nIf a target provides a target description including registers from the\nXSAVE extended region, but does not provide an XSAVE layout, use a\nfallback XSAVE layout based on the included registers.  This fallback\nlayout matches GDB's behavior in earlier releases which assumes the\nlayout from Intel CPUs.\n\nThis fallback layout is currently only used for remote targets since\nnative targets which support XSAVE provide an explicit layout derived\nfrom CPUID.\n\nPR gdb/30912\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id=30912\nApproved-By: Simon Marchi <simon.marchi@efficios.com>","shortMessageHtmlLink":"i386: Use a fallback XSAVE layout for remote targets"}},{"before":"119e02b106684797604b7b9d13c150eade65636d","after":"d9eb7e9563b49d36448a94177333640c4e534fd6","ref":"refs/heads/xsave_fallback","pushedAt":"2023-11-21T22:00:54.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"i386: Use a fallback XSAVE layout for remote targets\n\nIf a target provides a target description including registers from the\nXSAVE extended region, but does not provide an XSAVE layout, use a\nfallback XSAVE layout based on the included registers.  This fallback\nlayout matches GDB's behavior in earlier releases which assumes the\nlayout from Intel CPUs.\n\nThis fallback layout is currently only used for remote targets since\nnative targets which support XSAVE provide an explicit layout derived\nfrom CPUID.","shortMessageHtmlLink":"i386: Use a fallback XSAVE layout for remote targets"}},{"before":null,"after":"119e02b106684797604b7b9d13c150eade65636d","ref":"refs/heads/xsave_fallback","pushedAt":"2023-11-21T21:59:47.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"i386: Use a fallback XSAVE layout for remote targets\n\nIf a target provides a target description including registers from the\nXSAVE extended region, but does not provide an XSAVE layout, use a\nfallback XSAVE layout based on the included registers.  This fallback\nlayout matches GDB's behavior in earlier releases which assumes the\nlayout from Intel CPUs.\n\nThis fallback layout is currently only used for remote targets since\nnative targets which support XSAVE provide an explicit layout derived\nfrom CPUID.","shortMessageHtmlLink":"i386: Use a fallback XSAVE layout for remote targets"}},{"before":"2c1e03b4520e908aa1eb36ecda279047b17bab23","after":"97b29a61f7f001550fe985bf2deea1550e3c20dd","ref":"refs/heads/master","pushedAt":"2023-11-21T19:46:37.000Z","pushType":"push","commitsCount":255,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"bpf: Fixed register parsing disambiguating with possible symbol.\n\nThis changes parse_bpf_register to detect possible symbols that start with valid\nregister name, however due some following characters are not.\nAlso changed the regs-for-symbols-pseudo.s, adding some entries that\nshould not error if parser is properly detecting the symbol.","shortMessageHtmlLink":"bpf: Fixed register parsing disambiguating with possible symbol."}},{"before":"8375fdfe4cb64aa15aa635b05e133dccc86de933","after":"2c1e03b4520e908aa1eb36ecda279047b17bab23","ref":"refs/heads/master","pushedAt":"2023-10-27T18:50:20.000Z","pushType":"push","commitsCount":102,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"gdb: trim trailing spaces in i386-tdep.{c,h}\n\nChange-Id: I06c2e7c958c3451f00c70978538c1c2ad1b566df","shortMessageHtmlLink":"gdb: trim trailing spaces in i386-tdep.{c,h}"}},{"before":"ee1cb49e5a9de8049d887abd8c9f2eff1851147e","after":"8375fdfe4cb64aa15aa635b05e133dccc86de933","ref":"refs/heads/master","pushedAt":"2023-10-16T23:33:39.000Z","pushType":"push","commitsCount":55,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"gdb: remove unnecessary declarations in target.c\n\nI found that these local declarations were not needed, remove them.\nTested by rebuilding.\n\nChange-Id: I8d4fd0839ee1063b91dc002216d683aee0d4be22","shortMessageHtmlLink":"gdb: remove unnecessary declarations in target.c"}},{"before":"fef38782af55c22f542c8e0c80a1a932f2bbb892","after":"713e652caa49a80e273cb47fa58fafac3789db64","ref":"refs/heads/nt_x86_cpuid","pushedAt":"2023-10-09T17:59:18.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"{amd64,i386}-linux-tdep: Include NT_X86_CPUID notes in core dumps from gcore\n\nOverride the gdbarch make_corefile_notes method for the Linux x86\narches with a new function that calls linux_make_corefile_notes and\nx86_elf_make_cpuid_note to generate the core dump notes.","shortMessageHtmlLink":"{amd64,i386}-linux-tdep: Include NT_X86_CPUID notes in core dumps fro…"}},{"before":"5c9af5eaf25d5e30af1340b11e14d2e14ea25b5a","after":"fef38782af55c22f542c8e0c80a1a932f2bbb892","ref":"refs/heads/nt_x86_cpuid","pushedAt":"2023-10-09T17:53:04.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"fixup! x86-linux-nat: Support fetching TARGET_OBJECT_X86_CPUID objects","shortMessageHtmlLink":"fixup! x86-linux-nat: Support fetching TARGET_OBJECT_X86_CPUID objects"}},{"before":"ea186080fe2b94b21f3ac8ad7941948211d5e67a","after":"ee1cb49e5a9de8049d887abd8c9f2eff1851147e","ref":"refs/heads/master","pushedAt":"2023-10-09T16:20:36.000Z","pushType":"push","commitsCount":158,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"Fix: A potential null_pointer_deference bug\n\n  PR 30954\n  * ldlang.c (map_input_to_output_sections): Check that os is non NULL before using it.","shortMessageHtmlLink":"Fix: A potential null_pointer_deference bug"}},{"before":"8ba9d8fcf8403b45a38c0c78253205cc43031b55","after":"5c9af5eaf25d5e30af1340b11e14d2e14ea25b5a","ref":"refs/heads/nt_x86_cpuid","pushedAt":"2023-10-09T16:20:09.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"{amd64,i386}-linux-tdep: Include NT_X86_CPUID notes in core dumps from gcore\n\nOverride the gdbarch make_corefile_notes method for the Linux x86\narches with a new function that calls linux_make_corefile_notes and\nx86_elf_make_cpuid_note to generate the core dump notes.","shortMessageHtmlLink":"{amd64,i386}-linux-tdep: Include NT_X86_CPUID notes in core dumps fro…"}},{"before":null,"after":"8ba9d8fcf8403b45a38c0c78253205cc43031b55","ref":"refs/heads/nt_x86_cpuid","pushedAt":"2023-10-06T22:41:59.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"gdb: Use NT_X86_CPUID in x86 FreeBSD architectures to read XSAVE layouts\n\nIf this core dump note is present, use it to determine the layout of\nXSAVE register set notes.","shortMessageHtmlLink":"gdb: Use NT_X86_CPUID in x86 FreeBSD architectures to read XSAVE layouts"}},{"before":"0789a13f8af55f58cb97ca7d61fe0480512728c3","after":"ea186080fe2b94b21f3ac8ad7941948211d5e67a","ref":"refs/heads/master","pushedAt":"2023-09-26T20:38:39.000Z","pushType":"push","commitsCount":277,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"gdb/testsuite: add xfail for gdb/29965 in gdb.threads/process-exit-status-is-leader-exit-status.exp\n\nBug 29965 shows on a Linux kernel >= 6.1, that test fails consistently\nwith:\n\n    FAIL: gdb.threads/process-exit-status-is-leader-exit-status.exp: iteration=0: continue (the program exited)\n    ...\n    FAIL: gdb.threads/process-exit-status-is-leader-exit-status.exp: iteration=9: continue (the program exited)\n\nThis is due to a change in Linux kernel behavior [1] that affects\nexactly what this test tests.  That is, if multiple threads (including\nthe leader) call SYS_exit, the exit status of the process should be the\nexit status of the leader.  After that change in the kernel, it is no\nlonger the case.\n\nAdd an xfail in the test, based on the Linux kernel version.  The goal\nis that if a regression is introduced in GDB regarding this feature, it\nshould be caught if running on an older kernel where the behavior was\nconsistent.\n\n[1] https://bugzilla.suse.com/show_bug.cgi?id=1206926\n\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id=29965\nChange-Id: If6ab7171c92bfc1a3b961c7179e26611773969eb\nApproved-By: Tom de Vries <tdevries@suse.de>","shortMessageHtmlLink":"gdb/testsuite: add xfail for gdb/29965 in gdb.threads/process-exit-st…"}},{"before":"65d55e93df4d5bbb55f33d14ba2a7ef64b96f50c","after":"a43494a9edbe1f773d2ba289e371bb45a0a06ae4","ref":"refs/heads/kgdb-13","pushedAt":"2023-09-01T23:43:22.000Z","pushType":"push","commitsCount":8,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"aarch64: Remove incorrect sp adjustment for new-born kthreads","shortMessageHtmlLink":"aarch64: Remove incorrect sp adjustment for new-born kthreads"}},{"before":"b3e174482ffd731ab9a990aa233656b7427f8c61","after":"0789a13f8af55f58cb97ca7d61fe0480512728c3","ref":"refs/heads/master","pushedAt":"2023-08-28T22:27:31.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"bsdjhb","name":"John Baldwin","path":"/bsdjhb","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/8976613?s=80&v=4"},"commit":{"message":"[gdb/testsuite] Improve xfail in gdb.cp/nsusing.exp\n\nIn test-case gdb.cp/nsusing.exp I came across these xfails without PRMS\nmentioned:\n...\nXFAIL: gdb.cp/nsusing.exp: print x, before using statement\nXFAIL: gdb.cp/nsusing.exp: print x, only using M\n...\n\nAdd the missing PRMS, such that we have:\n...\nXFAIL: gdb.cp/nsusing.exp: print x, before using statement (PRMS gcc/108716)\nXFAIL: gdb.cp/nsusing.exp: print x, only using M (PRMS gcc/108716)\n...\nand limit the xfail to unfixed versions.\n\nThe PR is fixed starting gcc 13, but it has been backported to release\nbranches stretching back to gcc 10.  For simplicity we just stick to testing\nfor the major version and ignore the backported fixes.\n\nTested on x86_64-linux.\n\nApproved-By: Tom Tromey <tom@tromey.com>","shortMessageHtmlLink":"[gdb/testsuite] Improve xfail in gdb.cp/nsusing.exp"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOC0wNVQxNjozOTozOS4wMDAwMDBazwAAAASSQGF-","endCursor":"Y3Vyc29yOnYyOpK7MjAyMy0wOC0yOFQyMjoyNzozMS4wMDAwMDBazwAAAAN0Y86A"}},"title":"Activity · bsdjhb/gdb"}