Looks good, Chris. The only issue I see is that gdb isn't providing
the wrapper around ps (b2g-ps). I suggest:
“gdb is a command line debugger that provides a number of useful
options for debugging Firefox OS applications. Another useful tool,
b2g-ps, is a wrapper around the standard ps tool that shows app names
for each process running on an instance of B2G. The article shows what
options are available in gdb, and how to perform some common Firefox OS
debugging tasks.”
On Wed 04 Dec 2013 07:21:33 AM EST, Chris Mills wrote:
Thanks for your help Andrew! I’ve updated the article summary to:
“gdb is a command line debugger, which also provides a wire protocol. It
provides a number of useful options for debugging Firefox OS applications, such
as an extension to the standard ps tool that shows app names for each process
running on an instance of B2G. The article shows what options are available in
gdb, and how to perform some common Firefox OS debugging tasks.”
Does that work for everyone? I’d still love some input from anyone in the know
in filling in some of the missing details in the article.
All the best,
Chris Mills
Senior tech writer || Mozilla
developer.mozilla.org || MDN
cmi...@mozilla.com || @chrisdavidmills
On 3 Dec 2013, at 18:08, Andrew Overholt <overh...@mozilla.com> wrote:
OTTOMH: gdb is a command line debugger (it also provides a wire protocol). ps
is the standard *nix process listing tool.
I haven't read the article, sorry.
On Tue 03 Dec 2013 12:53:19 PM EST, Chris Mills wrote:
The MDN article has got an "unfinished draft” flag at the top of it, and the
article summary is sadly lacking - it doesn’t really tell you what the tools are.
Can someone give me a two sentence summary of what gdb/ps do, and let me know
what’s missing from the article? I’d be happy to help improve it.
Chris Mills
Senior tech writer || Mozilla
developer.mozilla.org || MDN
cmi...@mozilla.com || @chrisdavidmills
On 3 Dec 2013, at 16:44, Dave Hylands <dhyla...@mozilla.com> wrote:
Hi Soledad,
There is no other documentation for b2g-ps.
Regular ps produces way more output than most people need.
It also shows all of the child-content processes as merely plugin-container
Basically, the single most useful thing that b2g-ps does is to show the app
name associated with a given child-content process.
And it only shows the b2g process and its direct descendants.
b2g-ps passes on any options to ps, the most useful of which is the -t option.
This allows you to see the threads within a process.
There is another related utility called b2g-info, which dumps out a bunch of
memory information about the b2g processes as well. We include the
b2g-info output when you grab an about:memory dump.
Dave Hylands
----- Original Message -----
From: "Andrew Overholt" <overh...@mozilla.com>
To: "Soledad Penadés" <s...@mozilla.com>
Cc: dev-webapps@lists.mozilla.org, "Dave Hylands" <dhyla...@mozilla.com>
Sent: Tuesday, December 3, 2013 7:15:00 AM
Subject: Re: Is b2g-ps documented anywhere?
Dave can probably provide some info here.
On Tue 03 Dec 2013 06:34:42 AM EST, Soledad Penadés wrote:
Hi all
Heard about b2g-ps for the first time thanks to Kumar's answer to
Bosko, and it intrigued me.
However I can hardly find any documentation other than its source[1]
and a page in MDN[2]. Seems like a wrapper around the native ps to
discriminate against non b2g processes, am I right?
[1] Here's its source, I believe:
https://github.com/mozilla-b2g/gonk-misc/blob/master/b2g-ps
[2] MDN debugging with GDB
https://developer.mozilla.org/en-US/Firefox_OS/Debugging/Debugging_B2G_using_gdb
thanks!
_______________________________________________
dev-webapps mailing list
dev-webapps@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-webapps
_______________________________________________
dev-webapps mailing list
dev-webapps@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-webapps
