Re: Minor dbxout.c changes

[Daniel Berlin <dan at cgsoftware dot com>]

kenner@vlsi1.ultra.nyu.edu (Richard Kenner) writes:

>     the automated tester found:
> 
>     The new failures are:
>     powerpc-eabisim gdb.sum gdb.c++/ovldbreak.exp:
> 
> Are you sure that's my change?  There are a lot of other changes in
> that batch.
> 
>     I don't really understand the interaction between stabs, c++, and
>     overloaded functions.  Could you look at it?
> 
> I don't understand it *at all*, but I'll see if I can see anything
> obvious.

Don't bother.  C++ overloading with stabs is a hack at best, anyway.

For STABS, we first smash together some pieces to make a mangled name,
demanlge it, parse the arguments as if they were gdb expressions, to
attempt to get types from the arguments, and generate argument type
info from this.  This is just the beginning of the fun, but you can
already see how fragile it is.
You could have changed something simple, like, well, anything, and it
would break.  

The solution is to not use stabs with C++.  Don't kill yourself trying
to fix it, I don't spent more than 5 minutes on STABS+C++ bug reports
against gdb, because of how much time they tend to waste (there are
too many layers of bogosity involved).

-- 
"It's a good apartment because they allow pets.  I have a
Shetland pony named Nikkie.  Last summer Nikkie was involved in
a bizarre electrolysis accident.  All her hair was removed
except for her tail.  Now I rent her out to Hare Krishna family
picnics.
"-Steven Wright