Core dump on HP PA-RISC

[Dennis Handly]

>Does a memory debugger help here. Purify etc..
The rb tree is getting corrupted. What kind of a memory error this could be and how purify can help.

I was thinking you could try it.
Basically gdb will detect that you have overwritten the beginning or end of a heap region.

In your case, either you have a bad pointer that is pointing to all zeroes. Or someone has zeroed out your region.

You can detect the latter by taking the address in $r26 of your abort and putting a watchpoint on it.
watch *(long long*)$r26

[Dennis Handly]

>ME: putting a watchpoint on it.
watch *(long long*)$r26

If you want a hardware watchpoint you would need to display the value of $r26 of the abort and then paste that value into watch. Using $r26 literally gives you a glacially slow software watchpoint.
p /x $r26
watch {char} hex-address @ 16