From: Jerome Guitton <guitton@act-europe.fr>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] win32: bfd_cache_close after kill
Date: Thu, 17 Jun 2004 12:21:00 -0000 [thread overview]
Message-ID: <20040617132031.GA10371@act-europe.fr> (raw)
In-Reply-To: <20040524115048.GA27758@act-europe.fr>
[-- Attachment #1: Type: text/plain, Size: 356 bytes --]
> 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?
--
Jerome
[-- Attachment #2: inflow.c.dif --]
[-- Type: text/plain, Size: 1563 bytes --]
2004-06-17 Jerome Guitton <guitton@gnat.com>
* inflow.c (kill_command): release file handles in BFD.
* Makefile.in: Update inflow.c's dependencies.
Index: inflow.c
===================================================================
RCS file: /cvs/src/src/gdb/inflow.c,v
retrieving revision 1.22
diff -u -p -r1.22 inflow.c
--- inflow.c 28 Apr 2004 16:36:25 -0000 1.22
+++ inflow.c 17 Jun 2004 12:16:08 -0000
@@ -21,6 +21,7 @@
Boston, MA 02111-1307, USA. */
#include "defs.h"
+#include "bfd.h"
#include "frame.h"
#include "inferior.h"
#include "command.h"
@@ -597,6 +598,8 @@ kill_command (char *arg, int from_tty)
else
print_stack_frame (get_selected_frame (), 1, SRC_AND_LOC);
}
+
+ bfd_cache_close_all ();
}
\f
/* Call set_sigint_trap when you need to pass a signal on to an attached
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.587
diff -u -p -r1.587 Makefile.in
--- Makefile.in 14 Jun 2004 20:40:39 -0000 1.587
+++ Makefile.in 17 Jun 2004 12:16:08 -0000
@@ -1964,7 +1964,7 @@ inf-loop.o: inf-loop.c $(defs_h) $(infer
$(event_top_h) $(inf_loop_h) $(remote_h)
inflow.o: inflow.c $(defs_h) $(frame_h) $(inferior_h) $(command_h) \
$(serial_h) $(terminal_h) $(target_h) $(gdbthread_h) $(gdb_string_h) \
- $(inflow_h)
+ $(inflow_h) $(bfd_h)
infptrace.o: infptrace.c $(defs_h) $(frame_h) $(inferior_h) $(target_h) \
$(gdb_string_h) $(regcache_h) $(gdb_wait_h) $(command_h) \
$(gdb_dirent_h) $(gdbcore_h) $(gdb_stat_h)
next prev parent reply other threads:[~2004-06-17 12:21 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 [this message]
2004-06-17 20:13 ` Andrew Cagney
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=20040617132031.GA10371@act-europe.fr \
--to=guitton@act-europe.fr \
--cc=gdb-patches@sources.redhat.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