Provide a useful error message on running out of memory

[DemiMarie]

CMark aborts the whole process when it runs out of memory. This is a reasonable decision, but currently it just calls abort(), which leaves the user with no clue what happened.

CMark should instead write a useful error message to stderr (and possibly a backtrace, if one is easy to obtain) before aborting, or else recover from the error.