From: Eli Zaretskii <eliz@gnu.org>
To: Jerome Guitton <guitton@adacore.com>
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: Setting up GDB init files broken in DJGPP
Date: Fri, 17 Apr 2009 19:10:00 -0000 [thread overview]
Message-ID: <83ab6fjdus.fsf@gnu.org> (raw)
In-Reply-To: <20090417174113.GA4851@adacore.com>
> Date: Fri, 17 Apr 2009 19:41:13 +0200
> From: Jerome Guitton <guitton@adacore.com>
> Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sourceware.org
>
> I confirm that the fix that you suggest is OK:
> moving get_init_files before gdb_init was obviously an error. I've
> tested the patch in attachment, it works fine and the testsuite showed
> no regression on x86-linux. Can you confirm that it fixes the problem
> you are seeing?
Yes, it does. Thanks.
next prev parent reply other threads:[~2009-04-17 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 17:32 Eli Zaretskii
2009-04-17 17:41 ` Jerome Guitton
2009-04-17 19:10 ` Eli Zaretskii [this message]
2009-04-22 19:38 ` Joel Brobecker
2009-04-22 20:22 ` Jerome Guitton
2009-04-22 20:26 ` Joel Brobecker
2009-04-27 10:25 ` Jerome Guitton
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=83ab6fjdus.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=guitton@adacore.com \
/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