Re: GDB 10.1 release: branching early July?

[Joel Brobecker <brobecker@adacore.com>]

Hi Philippe,

> > I have a few things that IMO would be nice (or needed) in 10.1:
> > 
> > Default args for alias.
> > I have just sent the RFAv7 that implements
> > the prevention of an alias of an alias that has default args,
> > as suggested by Simon:
> > https://sourceware.org/pipermail/gdb-patches/2020-June/169467.html

Being a new feature, it's tough to justify waiting for it.. But
since we are looking at version 7 of the patches series, let's hope
that we can converge quickly on that one. There are some other issues
that look a bit difficult to resolve.

> > There are 2 things still to look at for the 'exec-file-mismatch':
> > 
> > * Below fixes a regression due to using build-id in exec-file-mismatch:
> https://sourceware.org/pipermail/gdb-patches/2020-June/169287.html

Indeed. It sounds useful to wait for that one.

> > * an opened PR for which some feedback is needed
> >    https://sourceware.org/bugzilla/show_bug.cgi?id=25475
> >   Note that possibly fixing this might change the user visible CLI.

This one is, erm, "interesting". I commented on the PR directly.
The short version is that I seem to be seeing the bug as being elsewhere,
so I asked for clarification. Regardless, at the moment, this seems
like this could be categorized as a relatively minor bug.

Still, worth keeping in our radar, since exec-file-mismatch is new
in GDB 10.

> > NB: I also have an RFC Improve handling of breakpoints with multiple locations.
> > https://sourceware.org/pipermail/gdb-patches/2020-May/168921.html
> > but no feedback received yet, so better for GDB 11.

I don't forsee any problems with the changes you propose. On the other
hand, I tend to agree with the general principle that it's safer to
make changes affecting existing output earlier in the release cycle.

-- 
Joel