Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
rogomatic help, rogue, etc
74 views
Skip to first unread message
songbird
Sep 20, 2014, 11:05:04 AM9/20/14
to
[adapted from post to comp.lang.c]
The new debugging/development season has started.
Help is appreciated. :) For fun. If I lose my
capital letters at times, sorry, bad habit i know.
Sometimes I wonder if there are people here who
are looking for some fun and challenging debugging?
The projects I've been tinkering with on and off
for the past several years could use help. Usually,
in the summer I am busy outdoors and with gardening,
but as cold weather approaches I start to dust off
things and try to find/fix bugs or to work on my
understanding of the code and various issues I have
detected.
This isn't homework, or even commercial in scope.
It is just fun for me. And I hope that I can find
people who would be willing to help with a few tasks
and tracking down a few sticky bugs.
The code I post as source to:
(see rogue and rogomatic versions marked LATEST for
the versions I'm at now)...
www.anthive.com/rog/rog.html
(the next is not as important unless you want to see
my scripts for generating backups of various things
and running the code in various ways and making bugs
replicable)...
Debugging bash scripts/code I post to:
www.anthive.com/rog/other/things.html
The format of the code/style was made by me at some
point because I was getting cross-eyed, I also expanded
a few macros out because I kept stumbling over them in
reading and hate to have to look up such simple things.
If you do debug and submit patches, try to follow the
style in the code. I wish I did have a site with git
to host this, but I do not have funds for it when I
already pay for the site I do have.
I code/debug on a Debian system setup using the most
recent tools in the testing suite. Things might still
work for older versions (stable aka Wheezy) of Debian
still. I'm uncertain about the other distributions
and status of things (like, I don't know if someone
has installed any of this on any Ubuntu systems) other
than one report about a non-Debian Mint 64 bit system
failing.
Here are some of my current tasks broken down into
several categories:
Environment/Porting:
- recently someone tried to get rogomatic running on
a non-Debian 64 bit system. No other details yet as
to why it failed. I don't have a 64 bit system for
testing/development so I won't get to this until I
upgrade my machine at some point.
- autotools related issues, I have been using what I
can from what has been provided, but I'm no wizard
with these, I'm sure another set of eyes on these
could get rid of old stuff that isn't used any more
and update them a bit. (currently, I cannot figure
out how to get curses debugging flags/libraries
through the rogomatic setup)
- supporting other OSes/Distributions...
Hard Failures (infinite loops, segfaults, workarounds, being stuck):
- rogue, infinite loop, when going down to the next
level, it gets stuck in function conn() in passages.c
not easy to reproduce
- rogomatic, the 1y repeat bug (currently worked around and set up
to eventually fatal error) (i think this is related to scrolling
messing up some record keeping things but to fix seems rather
intrusive, but don't let these hunches influence your research :) )
- rogomatic, starving in various ways
- rogomatic, repeated searching that misses obvious areas to search
harder
Cosmetic (things that show up strange on rogomatic screen, but are
represented correctly enough internally that it doesn't cause
failures, it just looks funny when they happen):
- rogomatic, passages sometimes are missing '#' characters
- rogomatic, monsters are sometimes not shown in the right spot or
are missing
- rogomatic, room displays sometimes leave behind '.' characters
when they should be erased
- rogomatic, repeats display of a pack item for no reason (I had this
fixed at one time, but lost those changes, grr!) a simple one off
error I think
General (wishlist, improvements, etc):
- clean up some of my past changes to get rid of useless ANT tags
- rogomatic, weapon handling, I made one round of changes and thought
I had this sorted out, but missed one case and that was a bug I
introduced, for the moment I've commented out the problem code, but
I hope to fix this sometime
- rogomatic, once the weapon handling is figured out take that
approach and apply it to armor handling.
- fix the database bugs for handling items with the same (see
code changes in rogue to work around this for now)
- rogomatic, dealing with other versions of rogue than the one I post
(I recently tried some of this but found the changes too intrusive
for the debian bsdgames-nonfree rogue -- the interface was too
different), I also tried some other older versions of rogue as
provided by the RRP and coredumpcentral, but these didn't get
very far or seemed to stick in the same sort of way, decided to
let this go for now and get back to bug fixing in rogomatic and
the rogue version I have as that goes the best for me)...
- see the TODO list...
Ok, sorry to be so long on this, but I suppose if you weren't
interested you wouldn't be reading this far. :)
I much prefer usenet to e-mail, so I would like to follow up this
to the rogue newsgroups, but I won't set followups yet. I'll make
a separate post there...
Questions about the code, debugging code/scripts, etc. welcome,
but sometimes I'm away from the computer for a day or two. Much
prefer it to happen on the rogue newsgroup so that I don't have to
repeat myself too much. And I must also admit that some of the code
is beyond my understanding at times. I may actually be wrong...
oops.
Thanks! You will get public honors for fixes, that is about all
I can promise. :) Changes will fall under the GNU license as it
is, I don't want to clutter things up by having multiple licenses...
songbird
The new debugging/development season has started.
Help is appreciated. :) For fun. If I lose my
capital letters at times, sorry, bad habit i know.
Sometimes I wonder if there are people here who
are looking for some fun and challenging debugging?
The projects I've been tinkering with on and off
for the past several years could use help. Usually,
in the summer I am busy outdoors and with gardening,
but as cold weather approaches I start to dust off
things and try to find/fix bugs or to work on my
understanding of the code and various issues I have
detected.
This isn't homework, or even commercial in scope.
It is just fun for me. And I hope that I can find
people who would be willing to help with a few tasks
and tracking down a few sticky bugs.
The code I post as source to:
(see rogue and rogomatic versions marked LATEST for
the versions I'm at now)...
www.anthive.com/rog/rog.html
(the next is not as important unless you want to see
my scripts for generating backups of various things
and running the code in various ways and making bugs
replicable)...
Debugging bash scripts/code I post to:
www.anthive.com/rog/other/things.html
The format of the code/style was made by me at some
point because I was getting cross-eyed, I also expanded
a few macros out because I kept stumbling over them in
reading and hate to have to look up such simple things.
If you do debug and submit patches, try to follow the
style in the code. I wish I did have a site with git
to host this, but I do not have funds for it when I
already pay for the site I do have.
I code/debug on a Debian system setup using the most
recent tools in the testing suite. Things might still
work for older versions (stable aka Wheezy) of Debian
still. I'm uncertain about the other distributions
and status of things (like, I don't know if someone
has installed any of this on any Ubuntu systems) other
than one report about a non-Debian Mint 64 bit system
failing.
Here are some of my current tasks broken down into
several categories:
Environment/Porting:
- recently someone tried to get rogomatic running on
a non-Debian 64 bit system. No other details yet as
to why it failed. I don't have a 64 bit system for
testing/development so I won't get to this until I
upgrade my machine at some point.
- autotools related issues, I have been using what I
can from what has been provided, but I'm no wizard
with these, I'm sure another set of eyes on these
could get rid of old stuff that isn't used any more
and update them a bit. (currently, I cannot figure
out how to get curses debugging flags/libraries
through the rogomatic setup)
- supporting other OSes/Distributions...
Hard Failures (infinite loops, segfaults, workarounds, being stuck):
- rogue, infinite loop, when going down to the next
level, it gets stuck in function conn() in passages.c
not easy to reproduce
- rogomatic, the 1y repeat bug (currently worked around and set up
to eventually fatal error) (i think this is related to scrolling
messing up some record keeping things but to fix seems rather
intrusive, but don't let these hunches influence your research :) )
- rogomatic, starving in various ways
- rogomatic, repeated searching that misses obvious areas to search
harder
Cosmetic (things that show up strange on rogomatic screen, but are
represented correctly enough internally that it doesn't cause
failures, it just looks funny when they happen):
- rogomatic, passages sometimes are missing '#' characters
- rogomatic, monsters are sometimes not shown in the right spot or
are missing
- rogomatic, room displays sometimes leave behind '.' characters
when they should be erased
- rogomatic, repeats display of a pack item for no reason (I had this
fixed at one time, but lost those changes, grr!) a simple one off
error I think
General (wishlist, improvements, etc):
- clean up some of my past changes to get rid of useless ANT tags
- rogomatic, weapon handling, I made one round of changes and thought
I had this sorted out, but missed one case and that was a bug I
introduced, for the moment I've commented out the problem code, but
I hope to fix this sometime
- rogomatic, once the weapon handling is figured out take that
approach and apply it to armor handling.
- fix the database bugs for handling items with the same (see
code changes in rogue to work around this for now)
- rogomatic, dealing with other versions of rogue than the one I post
(I recently tried some of this but found the changes too intrusive
for the debian bsdgames-nonfree rogue -- the interface was too
different), I also tried some other older versions of rogue as
provided by the RRP and coredumpcentral, but these didn't get
very far or seemed to stick in the same sort of way, decided to
let this go for now and get back to bug fixing in rogomatic and
the rogue version I have as that goes the best for me)...
- see the TODO list...
Ok, sorry to be so long on this, but I suppose if you weren't
interested you wouldn't be reading this far. :)
I much prefer usenet to e-mail, so I would like to follow up this
to the rogue newsgroups, but I won't set followups yet. I'll make
a separate post there...
Questions about the code, debugging code/scripts, etc. welcome,
but sometimes I'm away from the computer for a day or two. Much
prefer it to happen on the rogue newsgroup so that I don't have to
repeat myself too much. And I must also admit that some of the code
is beyond my understanding at times. I may actually be wrong...
oops.
Thanks! You will get public honors for fixes, that is about all
I can promise. :) Changes will fall under the GNU license as it
is, I don't want to clutter things up by having multiple licenses...
songbird
ant
Dec 18, 2014, 11:55:27 AM12/18/14
to
now at versions
rogue 1.1.1
rogomatic 2.0.1
debugging 3.0.0
things progressing as i get time.
ant
rogue 1.1.1
rogomatic 2.0.1
debugging 3.0.0
things progressing as i get time.
ant
ant
Dec 18, 2014, 12:24:00 PM12/18/14
to
ant wrote:
> now at versions
>
> rogue 1.1.1
> rogomatic 2.0.1
> debugging 3.0.0
forgot website links:
> now at versions
>
> rogue 1.1.1
> rogomatic 2.0.1
> debugging 3.0.0
www.anthive.com/rog/rog.html and
www.anthive.com/rog/other/things.html
ant
ant
Jul 17, 2015, 11:37:53 AM7/17/15
to
ant wrote:
...
for several months):
rogue 1.1.2
rogomatic 2.0.2
debugging 3.0.3
it being the summer season i'm not getting too much
done on tracking down bugs, but i am still testing the
compiling and such with the newer gcc and gcc-5
versions.
i've also been trying to see where rogue 5.4.5 is
stumbling (looks to be IO related as the player doesn't
look to be synching up with rogue), but there's a large
number of changes and i'm not having much luck doing a
quick search of all the changes between 5.4.4 and 5.4.5.
i've asked the author to send me a tar of their
repository as i'd like to be able to step through the
history and see where the problem has crept in. i haven't
yet found a way to get the whole archive with the change
history into git or svn from the site:
http://rogue.rogueforge.net/
i see there are some more recent changes to 3.6 in there
too that i'd like to try.
if i can get 5.4.5 going then perhaps i can get around
the bugs i'm hitting. or at least i can verify they are
still in there...
ant
...
> forgot website links:
>
> www.anthive.com/rog/rog.html and
> www.anthive.com/rog/other/things.html
now at versions (but not much has changed with these
>
> www.anthive.com/rog/rog.html and
> www.anthive.com/rog/other/things.html
for several months):
rogue 1.1.2
rogomatic 2.0.2
debugging 3.0.3
it being the summer season i'm not getting too much
done on tracking down bugs, but i am still testing the
compiling and such with the newer gcc and gcc-5
versions.
i've also been trying to see where rogue 5.4.5 is
stumbling (looks to be IO related as the player doesn't
look to be synching up with rogue), but there's a large
number of changes and i'm not having much luck doing a
quick search of all the changes between 5.4.4 and 5.4.5.
i've asked the author to send me a tar of their
repository as i'd like to be able to step through the
history and see where the problem has crept in. i haven't
yet found a way to get the whole archive with the change
history into git or svn from the site:
http://rogue.rogueforge.net/
i see there are some more recent changes to 3.6 in there
too that i'd like to try.
if i can get 5.4.5 going then perhaps i can get around
the bugs i'm hitting. or at least i can verify they are
still in there...
ant
elronnd
Jan 20, 2016, 7:40:27 PM1/20/16
to
On Sat, 20 Sep 2014, songbird wrote:
> *snip*
If you don't mind my asking, where did you get this code?
--
/\_/\
>( < < )< ,~. ,-.
>/ .Y. \< ,& ?_ i !
\ ^ /_,""._,~"'u > ~ | |
j / )_ : |
; Elronnd '--' ;
{_&-<`=_ /~"'-----"
\ f | f"'"'"'`~\ ;`
| | | | | | ; |
O_.' 0__, O__j d__'
> *snip*
If you don't mind my asking, where did you get this code?
--
/\_/\
>( < < )< ,~. ,-.
>/ .Y. \< ,& ?_ i !
\ ^ /_,""._,~"'u > ~ | |
j / )_ : |
; Elronnd '--' ;
{_&-<`=_ /~"'-----"
\ f | f"'"'"'`~\ ;`
| | | | | | ; |
O_.' 0__, O__j d__'
songbird
Jan 21, 2016, 5:07:23 AM1/21/16
to
elronnd wrote:
> On Sat, 20 Sep 2014, songbird wrote:
>> *snip*
>
> If you don't mind my asking, where did you get this code?
wow! someone read that?! :)
> On Sat, 20 Sep 2014, songbird wrote:
>> *snip*
>
> If you don't mind my asking, where did you get this code?
no, don't mind at all,
via:
https://code.google.com/p/rogomatic/
the website has changed since i last looked so they
are going into shutdown mode. i have early copies
with very few changes posted as:
rogomatic-r0.0.0.tar.gz
rogomatic-r0.0.1.tar.gz
etc.
and the framework versions (which i thought was just
silly so i figured out how to do things without that
extra layer of complexity):
rogomatic-fw-r0.0.0.tar.gz
rogomatic-fw-r0.0.1.tar.gz
etc.
i haven't been doing much with any of this lately,
too interested in other things. i did a compile and
run test the other day to make sure that process still
worked with recent gcc, ncurses, that's about it.
was thinking about starting up again this week but
keep getting distracted... :)
thanks for asking.
songbird
0 new messages