TT #179 (miniparrot segfault) caused by adding a method to an unused PMC?

[Mark Glines]

Does anyone have any idea why a miniparrot segfault could be caused by
adding a METHOD to a PMC which isn't even used by the rest of the system?

TiMBuS++ discovered that adding an "INTVAL" prefix to the "METHOD
get_type()" line (thereby making it not parse correctly) made the
segfaults go away on his x86-64 ubuntu machine.  The method in question
is pretty innocent, as far as I know.  I have no idea what's going on
here... hoping someone here on the list can help figure out the problem.
 Any takers?

Mark