[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[gforth] ORDER bug
From: |
Josh Grams |
Subject: |
[gforth] ORDER bug |
Date: |
Sat, 12 Nov 2011 22:03:57 -0500 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
I usually try to take a stab at fixing bugs myself, but I'm not sure
where to start with this one...
This happens both on my stock 0.7.0 and the CVS 0.7 (looks like I built
that on Oct. 15).
For some reason, above a particular address, doing the following fails
with an invalid memory address:
1088 allot wordlist >order order
:1: Invalid memory address
1088 allot wordlist >order >>>order<<<
Backtrace:
$B7945C88 @
$B7948F48 >does-code
$B7945724 interpret/compile?
$B7945788 (cfa>int)
$B7945888 (x>int)
$B79501B0 name>int
$B7977FF0
$B7950258 .voc
$0
$4
$B7947EEC execute
On 0.7.0, `216 allot` is the last safe address, and on my CVS version it
is `1084 allot`.
If you create a new definition after defining the wordlist, then ORDER
works fine again.
--Josh
- [gforth] ORDER bug,
Josh Grams <=
- Re: [gforth] ORDER bug, Josh Grams, 2011/11/12
- Re: [gforth] ORDER bug, Josh Grams, 2011/11/13
- Re: [gforth] ORDER bug, Bernd Paysan, 2011/11/13
- Re: [gforth] ORDER bug, Josh Grams, 2011/11/13
- Re: [gforth] ORDER bug, Bernd Paysan, 2011/11/13
- Re: [gforth] ORDER bug, Anton Ertl, 2011/11/17
- Re: [gforth] ORDER bug, Bernd Paysan, 2011/11/17
- Re: [gforth] ORDER bug, Anton Ertl, 2011/11/24
- Re: [gforth] ORDER bug, Bernd Paysan, 2011/11/25
- Re: [gforth] ORDER bug, Anton Ertl, 2011/11/17