From: John Baldwin <jhb@freebsd.org>
To: Simon Marchi <simark@simark.ca>
Cc: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: [PATCH 0/4] Support for 'info proc' on FreeBSD cores and native
Date: Wed, 03 Jan 2018 23:39:00 -0000 [thread overview]
Message-ID: <1595518.rlqukh4ycs@ralph.baldwin.cx> (raw)
In-Reply-To: <36f6c031e68bdd24294eeb188515a6d3@simark.ca>
On Wednesday, January 03, 2018 02:15:50 PM Simon Marchi wrote:
> > To be clear, which of these suggestions are you fine with?
> >
> > 1) Having a merged 'info proc stat/status' for FreeBSD.
>
> I am fine with this.
>
> > 2) Resurrecting 'info proc id' and 'info proc time'.
>
> I am fine with this, if you think it's useful. I didn't quite
> understand what it would show. If it just shows a subset of the
> information of stat/status, maybe it's not so useful, but if it's
> additional info, then sure.
Just a subset, so I'm fine with just skipping 2).
--
John Baldwin
prev parent reply other threads:[~2018-01-03 23:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 22:05 John Baldwin
2017-12-22 22:05 ` [PATCH 1/4] Create psuedo sections for FreeBSD NT_PROCSTAT_(PROC|FILES|VMMAP) notes John Baldwin
2017-12-27 1:18 ` Simon Marchi
2018-01-02 11:49 ` Nick Clifton
2017-12-22 22:05 ` [PATCH 3/4] Support 'info proc' for native FreeBSD processes John Baldwin
2017-12-27 2:23 ` Simon Marchi
2018-01-03 19:05 ` John Baldwin
2018-01-03 19:13 ` Simon Marchi
2018-01-03 21:56 ` John Baldwin
2017-12-22 22:05 ` [PATCH 2/4] Support 'info proc' for FreeBSD process core dumps John Baldwin
2017-12-27 1:56 ` Simon Marchi
2018-01-03 19:05 ` John Baldwin
2017-12-22 22:13 ` [PATCH 4/4] Document support for 'info proc' on FreeBSD John Baldwin
2017-12-23 8:46 ` Eli Zaretskii
2017-12-27 1:53 ` [PATCH 0/4] Support for 'info proc' on FreeBSD cores and native Simon Marchi
2018-01-03 19:05 ` John Baldwin
2018-01-03 19:15 ` Simon Marchi
2018-01-03 23:39 ` John Baldwin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1595518.rlqukh4ycs@ralph.baldwin.cx \
--to=jhb@freebsd.org \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).