> Now I have to confess I can't recall how to print all the thread
> callback stacks when 9vx breaks, not having had to do it for a year or
> so but ... I'm happy to set up a gdb for it and do what commands are
> needed should it break. Any recommendations here Russ?
thread apply all where
is the gdb command to get all stack traces.
> One other question -- anybody know how to create a 'tracking fork' in
> mercurial such that I can fork 9vx, but update from Russ's version to
> mine over time? I have some things I want to try out. I have not found
> a way to do this yet. The reason to do this "private repo" would be
> to have some other place to store my experiments than my laptop ...
Every checkout in Mercurial is a fork like that.
The easiest setup is to pick one such checkout
to be your coordination point.
hg clone http://code.swtch.com/vx32/ vx32-main
Then you can clone vx32-main and push to
and pull from it. When you want to update you
go into vx32-main and run hg pull, merge, and
then re-pull from your various clones.
If you are on another machine from where vx32-main
is, you can clone it with
hg clone ssh://kremvax//home/rminnich/vx32-main
Russ
