To clarify, is it literally "buffer overflow detected", or is it "buffer overflow adding in new fragment"?
If it's the latter, then the only suggestions I have are what's outlined in the FAQ. The fact that you're running linux in a VM on windows may mean that there are Windows settings that need to change as well. Though that likely depends on how you've got the VM networking setup, how you're mirroring traffic, etc.
If it's the former, then none of the settings in the FAQ are likely to help, as that's probably a glibc message, and is likely to indicate a problem somewhere.
In which case, if you can get me a backtrace of the crash, I can hopefully figure out what's happening and fix it. Or if it's not an actual bug, tell you what you need to do to get it working.
There are a couple ways to do this:
1) Get a core dump and load it into GDB
I'm not sure how Mint handles core dumps. On some distros, you can just do
root# ulimit -c unlmited
root# showeq
And then when it crashes a core file should be written to the directory where you ran it. You can then load the core dump into GDB with
gdb /path/to/showeq corefile
where corefile is the name of the core file (sometimes just core, sometimes core with the PID, or maybe something else depending on the distro)
But on other distros, there are extra steps (ubuntu, last I checked, uses apport, which changes core dump handling). So it gets a little more complicated.
2) Run showeq under GDB
gdb showeq
then once GDB starts and loads the executable, type 'run' and showeq should start.
In either case, once you've loaded the core file into GDB, or showeq running under GDB has crashed, you should be at a GDB prompt.
Type
thread apply all bt
And it will spew pages of backtrace info. It may or may not include identifying info about your character, server, etc., so I suggest not posting it publicly.
If you can copy/paste this into a private message to me, or paste it into a plain text doc and email it to
[email protected], then I can look at it.
Though, that said, I'm leaving on vacation later today, and won't be back for a couple of weeks. So I won't be able to get to it until I return.