This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 1/3] Move core_bfd to program space


>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:

Pedro> This moves the core_bfd global to be a field of the program space.  It
Pedro> then replaces core_bfd with a macro to avoid a massive patch -- the
Pedro> same approach taken for various other program space fields.

I am curious to know whether you would want to remove this macro in the
future.  I don't mean that you should do it -- just more a question of
what direction to go.  There are other macros like this too:
symfile_objfile, object_files, exec_bfd, ...

Also, I can't remember why I moved core_bfd to the progspace.  Would it
be better to have it just be a member of the target?  Or maybe in your
design these end up being basically equivalent, because core targets are
inherently single-process?

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]