Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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, 29 Jul 2004 20:02:00 -0000	[thread overview]
Message-ID: <410957E4.3000108@gnu.org> (raw)
In-Reply-To: <20040729150357.GA2697@act-europe.fr>

> Andrew Cagney (cagney@gnu.org):
> 
> 
>>>>> >>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...
>>>
>>>> >
>>>> >
>>
>>> Can it now go in the symbol-table reader that opened the file?
> 
> 
> I finally had time (at last!) to complete the implementation. New patch in
> attachment. Still no regression on i686 linux. OK to apply? 

Just a few tweaks.  Assuming there are still no regressions it's ok for 
mainline.

> 2004-07-29  Jerome Guitton  <guitton@gnat.com>
> 
> 	* inflow.c (kill_command): release file handles in BFD.
> 	* exec.c (exec_file_attach): release exec_bfd file handle.
> 	* symfile.c (symbol_file_add_with_addrs_or_offsets): release
> 	bfd file handle.
> 	* Makefile.in: Update inflow.c's dependencies.
> 
> Index: Makefile.in
> ===================================================================
> RCS file: /cvs/src/src/gdb/Makefile.in,v
> retrieving revision 1.596
> diff -u -p -r1.596 Makefile.in
> --- Makefile.in	23 Jul 2004 10:33:36 -0000	1.596
> +++ Makefile.in	29 Jul 2004 13:48:09 -0000
> @@ -1974,7 +1974,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)

"defs.h" includes "bfd.h" so this shouldn't be needed (same for the 
added #include "bfd.h" further down.


> Index: exec.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/exec.c,v
> retrieving revision 1.38
> diff -u -p -r1.38 exec.c
> --- exec.c	26 Jul 2004 14:52:59 -0000	1.38
> +++ exec.c	29 Jul 2004 13:48:09 -0000
> @@ -270,6 +270,8 @@ exec_file_attach (char *filename, int fr
>        if (deprecated_exec_file_display_hook)
>  	(*deprecated_exec_file_display_hook) (filename);
>      }
> +  if (exec_bfd)
> +    bfd_cache_close (exec_bfd);

Just call bfd_cache_close_all ()?

>  }
>  
>  /*  Process the first arg in ARGS as the new exec file.
> 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	29 Jul 2004 13:48:09 -0000
> @@ -21,6 +21,7 @@
>     Boston, MA 02111-1307, USA.  */
>  
>  #include "defs.h"
> +#include "bfd.h"

See above.

Again bfd_cache_close_all()?

> +  bfd_cache_close (abfd);

Andrew



  reply	other threads:[~2004-07-29 20:02 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
2004-06-24 10:52     ` Jerome Guitton
2004-07-29 14:04     ` Jerome Guitton
2004-07-29 20:02       ` Andrew Cagney [this message]
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=410957E4.3000108@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