I will try to find it. just to be sure..., this systems now runs
Redhat 6.1 & 6.2 without any problems for over a year now.
(I can build kernels without problems (I 've read the Signal 11 FAQ))
the only time I have a problem is when booting from the Redhat 7.0 kernel &
then run f.i. patch, dhcpcd and maybe others, but these two are the ones I ran
into.
the first when trying to beuild a new dhcpcd.
And it is not at random addresses AFAIK, the four time I tried to run path from
gdb it came with the same address.

I can't reproduce this here at all, with various different patch command lines,
package builds, etc.
This is with glibc-2.2-5. Is that what you're running? Could you give the
actual backtrace that gdb shows?

Eh right. That solves this one. That's an old one when I had troubles
upgrading a libc5 -> glibc environment. Appearantly this worked
until this release. That solves this issue..
(I've removed all programs that were installed in /usr/local... that have
copies in the /usr.. tree,)
Thanks a bunch, I ve learned a lot from the experience.
Still a question: where should ld.so be linked to? It is linked to the
ld-linux-1 environment.
I still have problems with DHCPCD as it accvio's but that one
is statically linked. I'm not a gdb wizzard so I still have to find out
where to get the symbols from etc.
The problem has been described in # 21542, no reactions there though.
Pump is no alternative because that doesn't allow me to update my firewall
rules when an address change is needed, and it gives me another address on
every boot.
The patch matter is closed as far as I'm concerned.
regards,
Nico Baggus