There's nothing wrong with your RAM, aside from what this particular
bit of code was trying to do with it.
The first part of the report is giving you some basic info, including
the name of the process that crashed. It also tells you which thread
the problem was in. EXC_BAD_ACCESS just means the program was trying
to do something it shouldn't, like read memory it isn't allowed to.
If you look at the part that says "Thread 4" it is telling you what
that thread was doing at the time. It's called a backtrace, the last
thing to execute is at the top and followed by all the nested
functions it took to get there. Then there is a bunch of low-level
CPU entrails, and more stuff about the exact code. I think all the
bit at the end has to do with libraries the binary was linked with,
but I'm guessing.
This stuff is most useful to the programmers who wrote the
application, but hardly at all to others (which is a large set that
includes most system administrators.)
If it keeps happening, then you've got a problem with servermgrd to
investigate. Actual bad RAM problems rarely crash things in such a
friendly and helpful fashion that the operating system has an
opportunity to output this handy report.
