[Prev][Next][Index][Thread]
ADB keyboards and Executor/NEXTSTEP 1.3
Hi Folks,
I'm a bit baffled. We still don't have an ADB based NEXT over here,
and I've received conflicting reports as to whether or not Executor
1.3 works with ADB based NEXTs. If you have piecked up E/NS 1.3, and
you have an ADB keyboard, I'd like you to do run Executor under gdb
if you can spare a few minutes.
You'll need to be root before you run gdb, so fire up Terminal (or
Stuart) and use the "su" command to become root.
Then type "gdb /LocalApps/Executor.app/Executor" and you should get
some messages and the "(gdb)" prompt. Double check that your version
of Executor 1.3 is the same as ours, by typing the following command:
x/2i 0x6572a
Gdb should reply with:
0x6572a: movel fp@(-272),d0
0x6572e: movel #2,d2
If you get something else, please verify that you're running E/NS
1.3, and send me e-mail and disregard the rest of this letter.
Now set a breakpoint at 0x6572e by typing the following command:
b * 0x6572e
gdb should respond with
Breakpoint 1 at 0x6572e
Now start executor with the "r" command, and then look at register
d0, by typing "p/d $d0". The conversation should look something like
this:
(gdb) r
Starting program: /LocalApps/Executor.app/Executor
Breakpoint 1, 0x6572e in ?? ()
(gdb) p/d $d0
$1 = 1
The big question is what does gdb say $1 is equal to? For ADB based
NeXTs, it should say "$1 = 2". However, I'd like to know what your
machine says, whether or not it says "$1 = 2". Additionally, I'd
like to know what versions of Word (if any) you've run with Executor
1.3, and whether or not the "q" key works for you.
There's a chance that the breakpoint will never be hit, and if that's
the case, I'd like to know that, as well.
E/NS 1.3a is still being tested, and is still awaiting potential ADB
mods, but I should be able to put it out on ftp.cs.unm.edu within a
couple days of tracking down the ADB problems, although it's hard to
tell just how long that will take.
--Cliff