Re: GDB BoF notes - GNU Cauldron 2023
Simon Marchi via Gdb <[email protected]>
| Newsgroups | gmane.comp.gdb.devel |
|---|---|
| Message-ID | <[email protected]> |
On 9/27/23 08:41, Pedro Alves wrote: > Hi all, > > We had a GDB BoF at the GNU Cauldron this past weekend, like in > previous years. > > I was positively surprised with the attendance and the engagement. > Thanks all! > > I took notes live while we were discussing. Thanks to Mark Wielaard > for letting me use this computer. :-) > > Below's an edited version of the notes, with some more details filled > in. Thanks a lot for taking notes! > =========== GDB BoF / GNU Cauldron 2023 =============== > > - Testsuite and CI discussion > > With either Linaro's CI and the sourceware.org buildbot, pre-commit, > post-commit, should breakages result in emails to mailing list? > > Are post-commit breakage emails sent to git author only? Should go > to git committer as well, for e.g., the scenario of a maintainer > applying a non-maintainer's patch. AI: Talk with Maxim Kuvyrkov > about it. > > Be mindful of overwhelming gdb-testers traffic. Counter argument > raised -- list is also used as results archive. If we decide not to send the breakage emails to gdb-patches, could we have a list we can subscribe to, to receive breakage emails? > - Revisiting defaults > > - Can we turn history saving on by default? Maybe default to > history on home dir by default, too (~/.gdb_history). That would > align us with bash. Some in the room have had this enabled in > their gdbinits for so long they no longer remembered this wasn't > on by default. Others weren't even aware you can turn this on. > > - Can we disable pagination by default? Surprisingly, no one in the > room expressed that they like pagination on. Sevearl people > mentioned that they have it off by default, and then use either > the terminal scroll function, or: > > "(gdb) pipe GDB_COMMAND | less" > > when necessary. I would be happy for these two changes to defaults to be made. Simon