On Mon, Jun 16, 2008 at 04:32:06AM +0100, Pedro Alves wrote:
A Sunday 15 June 2008 23:53:30, Christopher Faylor wrote:
I guess my basic question here is why is this needed at all? Does
the non-windows version of gdb have something similar? If so, this
should be patterned after that. If not, why is Windows special?
Well, with set "set verbose 1" you can see dll names being
read in already, but you also get a lot more. This is just a
couple of lines to add some debug output. Note that it
can't be much patterned (without some extra hair) other than
printing the so name, because the solib.c doesn't know a
thing about each solib's struct lm_info implementation. Then
again, I only suggested to add the image base to the output
because it was handy... Anyway, I've already spent more time
in this thread than it takes to add debug output locally
every time I'd need it. It's in Pierre's court to argue. ;-)
Ok. This is the kind of response I was looking for.
I'd like to have as little special case stuff in gdb as possible. We
have been moving in that direction and that's good.
"set debugevents" is a special case behavior for Windows gdb. I didn't
add it and I've wondered why it was necessary in the first place since I
don't recall ever feeling its lack on linux.
However, I guess I'll approve the patch since I can see why it would be
useful to have this information and it doesn't seem like there is
anything else that could be pressed into service in gdb-proper.