From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <4AC38470.5080500@maht0x0r.net> References: <20090930082306.GD5045@nipl.net> <3e1162e60909300745y4cd63102x8f861d34876fe4b4@mail.gmail.com> <20090930163010.f1377795.eekee57@fastmail.fm> <4AC38470.5080500@maht0x0r.net> Date: Wed, 30 Sep 2009 09:55:45 -0700 Message-ID: <13426df10909300955n1a62aab5o9f137d533112e01a@mail.gmail.com> From: ron minnich To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [9fans] 9vx is really excellent, link it on the bell-labs pages? Topicbox-Message-UUID: 79e6c466-ead5-11e9-9d60-3106f5b1d025 I think we owe the vx32/9vx guys some help here. So here's the question. 9vx is running. It breaks. How should we go about providing - useful diagnosis - useful backtracking There are some tools. Worst case, those of us who see it die from time to time could elect to run it under gdb for a while. No real pain there, and we could get some gain. For real pain but possible gain, we could run it under a function tracer. Even better, somebody using these tools might have a bright idea for debugging programs using vx32 or under 9vx and improve the process. 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? I see 9vx as a great tool, but, also, a great way for people to start mucking with the plan 9 kernel and learning. It's a great deal more approachable than Linux. And with 9vx there's no hardware required. 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 ... thanks ron