🚀 go-pugleaf

I've been bitten by this feature of the gcc loader twice now, and each
time it took forever to track down.  I save two compiled files in a
static object library, and sometimes I accidentally duplicate variable
names (I know, I know, poor programming practice).  These vars have
completely different types.  Anyhow, there are no error messages since
I'm not linking at that point.  Problem is, when I access the library
during a gcc load, it sets aside space for one of the variables, and
points both of them to this space.  Needless to say my programs crash
with random memory errors, usually long after the damage is done.

I'm at a loss to direct gcc in any way to tell me if there are
duplicate variable definitions in the library file when a do a load.
Further, I can't find any utilities that let me look at the library to
check its symbols, although there must be some around.  Any help here
on gcc's behavior?

Cheers --kk