From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <13426df10909300955n1a62aab5o9f137d533112e01a@mail.gmail.com> References: <20090930082306.GD5045@nipl.net> <3e1162e60909300745y4cd63102x8f861d34876fe4b4@mail.gmail.com> <20090930163010.f1377795.eekee57@fastmail.fm> <4AC38470.5080500@maht0x0r.net> <13426df10909300955n1a62aab5o9f137d533112e01a@mail.gmail.com> Date: Wed, 30 Sep 2009 10:55:42 -0700 Message-ID: Subject: Re: [9fans] 9vx is really excellent, link it on the bell-labs pages? From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Topicbox-Message-UUID: 79ec21ea-ead5-11e9-9d60-3106f5b1d025 > 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 =C2=A0yet. 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