Pike_interpreter.frame_pointer->pc should contain the start address in the assembler code.
/ Martin Stjernholm, Roxen IS
Previous text:
2002-10-08 21:45: Subject: more debug?
Try disassembling the bit before the offending instruction until you find a properly aligned starting instruction. A good rule of thumb is that if you get bad instructions "(bad)", i/o instructions (e.g. "in 0xe6,%al"), large adress offsets and/or strange segment overrides (e.g. "imul $0xffffffd0,%ss:0x2900d4a4(%eax),%ebx"), and similar strange thinks, you're either disassembling malaligned code, or 'extrons' of data inserted into the code (recognized by strange code that is never reached because the surrounding code always jumping around it).
You could also try stepping up into the next stack frame (which belonged to mega_apply) and see if any of the local variable values there give any hint of what module/class/valuetype was involved.
/ Leif Stensson, Lysator