Versioning mess proved!!!

[Geoff Keating]

> From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
> Date: Sun, 1 Oct 2000 13:47:14 +0200

> Well, I wish I knew exactly what happens...
> It seems that under some combinations of glibc-2.1.3/glibc-2.2 and thus a 
> mixture of NOTYPE/WEAK and FUNC/WEAK definitions the start of __gmon_start__ 
> gets relocated, whereas it should stay a 0. It get's relocated to an absolute 
> branch to address 0. Since now the test for 0 in call_gmon_start fails, 
> __gmon_start__ gets called and then branches to 0 which nicely segfaults.

Is __gmon_start__ defined anywhere?  If not, it should be zero.  If it
is, both should be the same.

> I'm not sure about the implications, but maybe this can be solved with the 
> appended patch? At least it shouldn't hurt to be explicit about the type of 
> __gmon_start__ and it looks a bit cleaner that way. I'll try that now on PPC.

I think this is just papering over a bug somewhere else.

-- 
- Geoffrey Keating <geoffk@cygnus.com>