these are the errors I get:
3 [main] smaug 2632 handle_exceptions: STATUS_ACCESS_VIOLATION
583 [main] smaug 2632 open_stackdumpfile: Dumping stack trace to smaug.exe.tackdump
what can I do?
I cannot help but ask: Do you seriously believe someone can give you a solution to this knowing only what little you've posted?
I don't mean to be rude (probably sounds as such, nonetheless. Apologies if so.) but you should really provide some of the following, at the *bare minimum*:
1) Codebase / version?
2) What were you doing when this happened?
I'm sure that if you can at least provide some information like that, people will be more than happy to help you.
ouch
Yes: well I'm trying to translate smaug 1.4 from english to italian.
I built new area files and new mobs.
I compile it in Cygwin (under winxp) and everything works fine (except some errors in work.c).
Then I run it and i receive that error.
-----------
(loading skills...done)
Mon May 2 20:48:22 2005 :: reading Planes File ...
Mon May 2 20:48:22 2005 :: loading area files ...
(help.are)
3 [main] smaug 1428 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
670 [main] smaug 1428 open_stackdumpfile: Dumping stack trace to smaug.exe.stackdump
-----------
I think there's something wrong with vnumbers or something... I tryed changing area files, but I had no success.
Ouch? Like I said, it wasn't meant to be harsh. There just wasn't enough information for me or anyone else to help you with the problem.
Now on to what you said. While I don't know the exact reason for the error you're getting, I suspect it may have something to do with a code change that you might have made. It seems like it's bombing when loading up the help.are (or perhaps at the very first one after that) and that definitely isn't a good sign.
If you've changed stock areas, especially the first one that should be loading after help.are, then you may need to either remove it or replace with stock and see if that fixes the problem. If it's not the area files, I'd take a look at the code and in particular whether or not those warnings you got are more serious.
Also, just my $.02, but I wouldn't try running something when I knew the compiler threw errors somewhere. Usually best to fix those first and get it to compile cleanly.
Hopefully that helps a little, if not maybe someone else will chime in with more suggestions.
I'm not that familar with Cygwin, and I don't think it dumps a core. So try booting up the mud in gdb and see if it sends any extra output that would be useful.