From: Andrew Cagney <cagney@gnu.org>
To: Jerome Guitton <guitton@act-europe.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] win32: bfd_cache_close after kill
Date: Thu, 17 Jun 2004 20:13:00 -0000 [thread overview]
Message-ID: <40D1FB3F.3060904@gnu.org> (raw)
In-Reply-To: <20040617132031.GA10371@act-europe.fr>
>>When the inferior is killed, it is safe the release the different file
>>> handles that BFD keeps open. It is particularly useful on Win32 (and
>>> presumably on HP UX) to be able to recompile and restart a new debugging
>>> session without quitting GDB...
>
>
> New implementation, using bfd_cache_close_all. No regression on i686
> linux. OK to apply?
Can it now go in the symbol-table reader that opened the file?
Andrew
next prev parent reply other threads:[~2004-06-17 20:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-24 10:50 Jerome Guitton
2004-05-24 17:07 ` Jerome Guitton
2004-05-25 9:24 ` Jerome Guitton
[not found] ` <40B4F5A2.9000708@gnu.org>
2004-06-01 9:26 ` Jerome Guitton
2004-06-08 19:49 ` Andrew Cagney
2004-06-17 12:21 ` Jerome Guitton
2004-06-17 20:13 ` Andrew Cagney [this message]
2004-06-24 10:52 ` Jerome Guitton
2004-07-29 14:04 ` Jerome Guitton
2004-07-29 20:02 ` Andrew Cagney
2004-07-30 12:08 ` [commit] " Jerome Guitton
2004-07-30 13:28 ` Andrew Cagney
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=40D1FB3F.3060904@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=guitton@act-europe.fr \
/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