Bug fix in `tree.c': build_range_type

[Jeffrey A Law]

  In message < 199807290855.KAA02925@esmeralda.gerwinski.de >you write:
  > > But shouldn't TYPE_SIZE_UNIT be initialized to zero by the make_node
  > > call which created the type?  There's a loop in that make_node that is
  > > supposed to zero out the node when it's allocated.
  > 
  > Indeed.  Very strange. :-(
Can you say memory corruption :(  If you've got an x86 linux box you
can probably set a hardware watchpoint on the memory location which
holds TYPE_SIZE_UNIT for the node in question to find out where it's
getting clobbered.

ie, put a conditional breakpoint in make_node just before it returns
the node in question.  get the address of the size_unit field.  Then
break *<hex address>

And let the program continue.


  > I am subscribed to EGCS (or at least hope to be subscribed) under the
  > address `peter.gerwinski@uni-essen.de'.  Since I got only two letters
  > through the EGCS lists (egcs, egcs-bugs, egcs-announce) since 20 July,
  > I suspect that there is something wrong.
That address is not subscribed either.

It is possible you subscribed, but were then unsubscribed because messages
to your address were bouncing.

I recommend you re-subscribe.

jeff