public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: John Baldwin <jhb@FreeBSD.org>
To: Rustam Kovhaev <rkovhaev@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [RFC PATCH] Add a new 'info proc time' subcommand of 'info proc'.
Date: Wed, 28 Jul 2021 08:00:28 -0700	[thread overview]
Message-ID: <d6afcce3-184a-7120-49e0-4e657a6108cd@FreeBSD.org> (raw)
In-Reply-To: <YQCD58zoQ89Ps04Q@nuc10>

On 7/27/21 3:08 PM, Rustam Kovhaev via Gdb-patches wrote:
> Sometimes (unfortunately) I have to review windows user-space cores in
> windbg, and there is one feature that I really want to implement in gdb,
> but I don't know whether it is a good idea or not, and why it has not
> yet been implemented in gdb.
> 
> In wdbg there is a .time command that gives me time when core was taken.
> I could not find the same functionality in gdb and in elf core.
> I know about kernel core_pattern and timestamp, and there are user-space
> daemons that write the timestamp, and sometimes if I am lucky I can get
> timestamp from modified/created file attributes and this solves the
> problem most of the time, but quite often I get only core.PID file +
> some app log and there is no way for me to figure out when exactly the
> core was taken.
> 
> Current patch does not take into account lots of things like endianness,
> cpu archs other than x86, other code paths, etc, and there is also
> kernel side to modify and coordinate, but it does work in my lab, and I
> was pretty happy to learn a little bit about the project.

Does the Linux kernel write out NT_TIME notes when creating core dumps
or would this command only work on cores generated by a patched gdb's
'gcore' command?

-- 
John Baldwin

  reply	other threads:[~2021-07-28 15:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 22:08 Rustam Kovhaev
2021-07-28 15:00 ` John Baldwin [this message]
2021-07-28 15:06   ` Rustam Kovhaev
2021-07-28 18:35     ` John Baldwin
2021-07-28 19:26       ` Rustam Kovhaev

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=d6afcce3-184a-7120-49e0-4e657a6108cd@FreeBSD.org \
    --to=jhb@freebsd.org \
    --cc=gdb-patches@sourceware.org \
    --cc=rkovhaev@gmail.com \
    /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).