This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: GDB 7.5.91 available for testing
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 13 Mar 2013 20:34:31 +0200
- Subject: Re: GDB 7.5.91 available for testing
- References: <20130312231727.GF31629@adacore.com> <8338vzjije.fsf@gnu.org> <20130313180220.GK3264@adacore.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Wed, 13 Mar 2013 11:02:20 -0700
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
>
> > I built this natively on Windows with 32-bit MinGW tools, and bumped
> > into a few issues.
>
> Thanks! Would you mind submitting each patch individually, so we can
> track them?
Done.
> If there are any that you feel you can self-approve, please also go
> ahead.
I need approval from DJ for the libiberty part. As for the other one,
I'd prefer to hear approval, since it's semi-kludgey.
> > Looks like it reads Python init files from the installed (previous)
> > GDB version, and barfs. How to tell it to use its own Python
> > files? It would be a nuisance not to be able to run GDB without
> > installing it first.
> >
> > Also, are the DWARF-related warnings serious or expected? (I'm
> > using GCC 4.7.2, the latest one available from MinGW.)
>
> We already discussed this, and many different ideas were suggested,
> but none that was satisfactory. You need to do what the testsuite does,
> which is change a setting, I just don't remember which.
Can anyone point me to the archives where this setting is described?
Thanks.
> So far, none of the issues that you listed appear blocking. Am I right?
Not blocking, although I'd prefer to have the warnings due to
pyerrors.h be fixed on the release branch.