Zugg Software :: View topic - [2.03] Using (%s) to capture spaces not working

Posted: Fri Sep 28, 2007 8:16 am

The behavior you described does occur. I'm not sure if it's a bug or not, but it's a result of using quotes(") with you #sub. If you use curly braces instead '{' (which I believe is the correct way to get variables evaluated), it works fine. As a matter of fact, the quote is supposed to treat everything as a literal so I'm surprised the variables are being evaluated at all. At any rate this is what you want.

Wanderer Joined: 14 Jul 2004 Posts: 83

I made the suggested change and the output did generate correctly for about 10 lines. After that, it generated a series of error messages including one about data being out of range (sorry, didn't think it would totally break my cmud so I didn't submit it) followed by 2 memory read violations. Continuing application through those got about 8 or 10 more lines out of the game before it caused my CMUD to stop. The memory did not max out (processor was around 12% at the time and the CMUD processes were both at 0), but the game would not allow me to do anything. I received no output from the game, could not click on any button, could not enter any text on the command line. I closed the process, re-opened CMUD, attempted to connect to the game again and within 1 second of connection, CMUD stopped again. Not even the ticktimer is showing any activity.

I closed the process again, re-opened CMUD, opened the session offline and changed the curly brackets back to quotes, reconnected and CMUD stopped again.

I attempted to open a new session that uses the same pkg file and received a "Canvas does not allow drawing error." That was the first error that had generated since the initial change and once I submitted the bug report and continued the app, CMUD stopped again.

Wizard Joined: 14 Aug 2004 Posts: 1269

If you've never submitted a particular error before and you believe it is not just an error in your script, you should always submit it.

Posted: Fri Sep 28, 2007 4:30 pm

Never, ever press the continue button when a crash happens. Okay, that's an exaggeration - in the past, there've been things that shouldn't have caused the crash dialogue to come up, but it did anyway - but all the things that're supposed to make the crash dialogue appear indicate some kind of memory corruption. CMUD can't normally recover from that kind of error, and that's why you're seeing all that weird behaviour when you continue.

Since CMUD's memory has been corrupted, it can cause all kinds of things to go wrong - try recreating this setting that's not working in the untitled session and using #show to run text through it. It's possible that it could be corruption in your package file, possibly caused by CMUD saving (or attempting to save) corrupt data after a crash.

Wizard Joined: 14 Aug 2004 Posts: 1269

Posted: Fri Sep 28, 2007 8:52 pm

Also, certainly never *Send* additional bug reports after you have already received a crash. Definitely send the first crash dump, but once CMUD has crashed once, sending additional crash dumps is usually pointless and just fills by crash dump database with unless reports.

The rule of thumb that I use is that I will click "Continue" if I'm in the middle of something on the MUD and want to try and get to a safer area. But the first chance that I can get, I will then exit CMUD and restart.

Enchanter Joined: 09 Sep 2007 Posts: 605

Zugg
Heh, and what to do if first bur report sending fails (unable to send bug report)? I usually send it again, it succeed on second try. Am I wrong? Can a bug report be sent partially or it like transaction, everything or nothing?
For me there is only 1 type of error after which I continue to run CMUD - help window index error (out of range).

SubAdmin Joined: 18 Nov 2001 Posts: 5182

If it fails to send save it to a file and post it. The file it saves to will be appended so make sure you grab the last report in the file, also remove any private information when posting. Be sure to use code tags as well.

Last time I tested it there was still a known bug with sending feedback and bug reports when using an HTTP proxy configured through the Internet Connection settings. Disabling that proxy configuration, sending the report, then reenabling works for this particular bug.

Enchanter Joined: 09 Sep 2007 Posts: 605

If it failed on first try, it works from second try. And I'm not sit behind any proxys. Just 50/50: may send on first try, or may only on second one.

Wizard Joined: 14 Aug 2004 Posts: 1269

If it fails to send check out bugreport.txt in your CMUD folder for the stack trace.

Wanderer Joined: 14 Jul 2004 Posts: 83

Update:

I had to work today so I couldn't get back to this until this evening. I took the following steps:

1. Uninstalled CMUD.
2. Deleted all left over files, including those in the My Games directory
3. Re-installed CMUD
4. Deleted all extraneous MUD sessions.
5. Created new session for the mud I play on
6. Copied a backed-up version of my original pkg file (It was backed up to a flash drive a month ago and the flash drive wasn't plugged in at the time of the borking)
7. Opened session
8. Made the changes originally suggested (changing " to { } in the one trigger)
9. Caused trigger to fire

Result - output is formatted correctly, no crashing. I cannot replicate the original crash at this time. If, however, it happens again, rest assured that a crash report will be sent.

thanks