-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Color crash bug #40
Comments
Looks like this is a bit more complex, but possibly more widespread. Standard status_attr gives an error for a bad color. Here are the lines that seem to be the most likely cuplrits, looking like the issue is in decode_attr(), str*(), or substr(). Need to do some investigation there. If you want to try it, the relevant code is in my scripts directory, you'll need vwstatus.tf (most likely culprit), vworld.tf, status.tf, and socket.tf https://github.com/warmstarter/tinyfugue-scripts
|
Here it is .....
|
Ok, here's a hint, this also works. Given that the @{ is unmatched, it shouldn't even be attempting anything.
|
This is fixed in #38 |
Found an easy way to crash TinyFugue.
This would be a pretty standard way to set colors in my status bar:
/set vw_tablist_fg_world_attrs=@{Cyellow,Cbgrgb001}
But if I just set it to a non-existent color:
/set vw_tablist_fg_world_attrs=@{Ctestyellow,Cbgrgb001}
And then change my fgworld to trigger the color change in the status bar, TF dumps core. Presumably similar would happen with any way of setting that invalid color. Looks like colors are just being passed for evaluation rather than sanity checked.
Haven't yet tested if I can get a MUSH to remotely crash TF with this bug, but seems likely.
The text was updated successfully, but these errors were encountered: