A bug is preventing me from ascending?
JRBrown
in Gehennom since forever and wrestled my human lawful Archaeologist
up to Astral for my very first ascension. I whistled my tame angel and
pet purple worms into position, #offered the amulet, and as I was
taking screenshots of the ending stats (Nethack Carbon does not permit
copy-paste), the game crashed.
Since Nethack Carbon on my system is annoyingly unstable, I had been
making backup savefiles frequently, and had one from just after
getting to the Plane of Earth, so I didn't have to redo much. The
second time around I made a savefile standing on the altar, just for
paranoia's sake. #offer, "Congratulations mortal!", DYWYPI?, aaaaand
crash again.
A little testing shows that I can ascend just fine in wizard mode, but
in either Explore or regular mode, after all the ending reports,
instead of the "Goodbye [name], you went to your reward..." message, I
get this message: "Postgame wrapup disrupted. Report error to
"wizard". Bad window id -1", then the game crashes without updating
the logfile or scores (I tried moving the logfile and high-score file;
no help).
I am using Nethack Carbon (official unpatched release, straight off
the website; I tried a fresh copy and it does the same thing), and it
acts the same running under both Mac OSX 10.3 and Mac Classic OS 9 (on
an old PowerMac G3 blue and white). Since I doubt that it is an issue
with Nethack Carbon as such (I know it's not the most popular version
but *someone* would have complained by now), I'm assuming that it is
something about my system or the game itself. Anyone have any advice?
Dirk Zimmermann
> So over the holiday I took one of my save games that has been parked
> in Gehennom since forever and wrestled my human lawful Archaeologist
> up to Astral for my very first ascension. I whistled my tame angel and
> pet purple worms into position, #offered the amulet, and as I was
> taking screenshots of the ending stats (Nethack Carbon does not permit
> copy-paste), the game crashed.
>
> Since Nethack Carbon on my system is annoyingly unstable, I had been
> making backup savefiles frequently, and had one from just after
> getting to the Plane of Earth, so I didn't have to redo much. The
> second time around I made a savefile standing on the altar, just for
> paranoia's sake. #offer, "Congratulations mortal!", DYWYPI?, aaaaand
> crash again.
>
> A little testing shows that I can ascend just fine in wizard mode, but
> in either Explore or regular mode, after all the ending reports,
> instead of the "Goodbye [name], you went to your reward..." message, I
> get this message: "Postgame wrapup disrupted. Report error to
> "wizard". Bad window id -1", then the game crashes without updating
That bad window id -1 actually hints at a problem in the carbon window
API part, not the core itself. It would be very interesting to know
whether your problem persists on the tty version (assuming save files
are compatible). Only have access to Intel Macs so I can't debug your
save file to make sure.
--
Dirk
http://blog.dirkz.com
Pat Rankin
[...]
> A little testing shows that I can ascend just fine in wizard mode, but
> in either Explore or regular mode, after all the ending reports,
> instead of the "Goodbye [name], you went to your reward..." message, I
> get this message: "Postgame wrapup disrupted. Report error to
> "wizard". Bad window id -1", then the game crashes without updating
> the logfile or scores (I tried moving the logfile and high-score file;
> no help).
That's a panic (nethack detected an error and decided
to quit), not a crash. There is a big difference. Your
nethack directory might have a file named "paniclog" which
contains entries for this, although it will only have the
same "bad window id" feedback you've already seen. It's
mainly for situations where that type of feedback hasn't
been noticed when delivered.
The only end of game problem I can think of offhand is
when you have an adjacent pet who can't follow due to being
stuck eating or trapped. By the time that point is reached,
nethack has closed the message window and the code that tells
you that your companion won't be coming along tries to send
the message to somewhere unreachable. I think that the tty
interface falls back to just sending a line to the terminal
(or window) as ordinary text, without telling you that
something is very wrong. Other interfaces may notice the
problem and panic; I'm not sure whether the old windowing Mac
one falls into that category but now suspect that it does....
I think it would be extremely surprising for you to hit
that problem more that once, even starting with a backup save
file from the same game. Perhaps there are other situations
where the core of the game tries to send a message after
telling the interface side of the game that it won't be doing
such. The pet situation has been fixed in the post-3.4.3
development code, but I think the fix is just to handle pets
sooner while the message window is intact, so wouldn't help
for any other circumstances which trigger this problem.
JRBrown
I'm pretty sure the Carbon savefiles aren't compatible with anything
else at all. Thanks, though.
JRBrown
> On Jan 5, 1:17 pm, JRBrown <juliana.rb.br...@gmail.com> wrote:
> [...]
>
> > A little testing shows that I can ascend just fine in wizard mode, but
> > in either Explore or regular mode, after all the ending reports,
> > instead of the "Goodbye [name], you went to your reward..." message, I
> > get this message: "Postgame wrapup disrupted. Report error to
> > "wizard". Bad window id -1", then the game crashes without updating
> > the logfile or scores (I tried moving the logfile and high-score file;
> > no help).
>
> when you have an adjacent pet who can't follow due to being
> that problem more that once, even starting with a backup save
> file from the same game.
OK, thanks. On both tries, I tried to ascend with 8 pets (all adjacent
squares), so that may have increased the chances of whatever it is
happening again. I'll redo the last stage of the run, and try
ascending sans pets, and see if I can get it to accept me this time...
JRBrown
Yay! It was indeed a pet-related issue (or at least it stopped
happening when I ditched the pets). Expect YAFAP shortly. Pat, you are
my new God. Let sacrifices be offered in your name. :)
JR
Doug Freyburger
>
> Yay! It was indeed a pet-related issue (or at least it stopped
> happening when I ditched the pets). Expect YAFAP shortly. Pat, you are
> my new God. Let sacrifices be offered in your name. :)
Current DevTeam members don't get listed in any pantheon. Maybe they
take #offer'ed patches? ;^)