Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 7.5.91 available for testing
Date: Wed, 13 Mar 2013 18:02:00 -0000	[thread overview]
Message-ID: <20130313180220.GK3264@adacore.com> (raw)
In-Reply-To: <8338vzjije.fsf@gnu.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? If there are any that you feel you can self-approve, please
also go ahead.

> 4. After I overcame all these issues, debugging GDB with itself
>    reveals more:
[...]
>    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.

So far, none of the issues that you listed appear blocking. Am I right?

-- 
Joel


  reply	other threads:[~2013-03-13 18:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130312231727.GF31629@adacore.com>
2013-03-13 17:50 ` Eli Zaretskii
2013-03-13 18:02   ` Joel Brobecker [this message]
2013-03-13 18:34     ` Eli Zaretskii
2013-03-13 18:58       ` Jan Kratochvil
     [not found] ` <5140904A.2040206@oarcorp.com>
     [not found]   ` <20130313181759.GN3162@adacore.com>
     [not found]     ` <201303141714.55981.vapier@gentoo.org>
2013-03-14 23:38       ` sim/erc32/Makefile.in patch - was " Joel Brobecker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130313180220.GK3264@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox