This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [0/17] RFC: share minimal symbols across objfiles
- From: Joel Brobecker <brobecker at adacore dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 4 Jan 2012 19:26:04 +0400
- Subject: Re: [0/17] RFC: share minimal symbols across objfiles
- References: <m3zkeu9868.fsf@fleche.redhat.com> <20111218063648.GF21915@adacore.com> <m3hb0sv5ec.fsf@fleche.redhat.com>
> It would be helpful to know which systems have this issue. Maybe we
> could make it a gdbarch parameter, so that we don't need workarounds on
> more capable systems.
Is exec-bfd the only objfile with the issue? To me, the answer seems
an obvious NOT, but you never know. Going back to this question,
I'm just going to repeat as a reminder that the only systems I remember
having file-locking problems that forced us to close fds are pa-hpux,
and Windows in general. The sort of issue I remember seeing was trying
to update the executable while the program is opened by GDB and yet
not running. I still haven't gotten to te bottom of some failures see
in GDB on GNU/Linux systems as well, with symptoms very similar to
a file-locking issue. I started looking at them when I had a free
second or two, but I could never make sense out of them in the short
amount of time I could dedicate.
The gdbarch parameter seems risky to me, it's often more a property
of the filesystem than a property of the platform...
Having spent a fair amount of time on many of these exotic platforms,
I would be happy to try helping a bit.
--
Joel