From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id ugyMOZtyAWEZIQAAWB0awg (envelope-from ) for ; Wed, 28 Jul 2021 11:07:07 -0400 Received: by simark.ca (Postfix, from userid 112) id DAE891EDFB; Wed, 28 Jul 2021 11:07:07 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 3D03C1E79C for ; Wed, 28 Jul 2021 11:07:07 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 7EF97395B02B for ; Wed, 28 Jul 2021 15:07:06 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7EF97395B02B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1627484826; bh=uUWmB0r+9SgNJhZhSnF9Hw+YBl9jEGqgbFcWxMl4BLE=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=DbnFzs2e3UjWh4nC41Ay8ev0KL1WNV+Y6ePShq8uACpLA8tEFZSwLSFjBW6NoR0W1 MBkviFr0wdw/9VLn+GFl839PpkQJvl9xEasM0fe44fgv3a3UIfY8Cj3XAKyNOr5tMr my2GsOUiwgimbh4hV3Sk4YK1U21mlI19kj1r/cvk= Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) by sourceware.org (Postfix) with ESMTPS id E319D3858039 for ; Wed, 28 Jul 2021 15:06:46 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org E319D3858039 Received: by mail-qk1-x72e.google.com with SMTP id t66so2552203qkb.0 for ; Wed, 28 Jul 2021 08:06:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=uUWmB0r+9SgNJhZhSnF9Hw+YBl9jEGqgbFcWxMl4BLE=; b=alvd26RLaJUjfKuNyLbyW8PduyPdCzbRlSvIRBxrAWoBYmYgpkEulVAvNk6AKCFTcI NDOpHberxvIO64wSJhxp95adQUguULEBq0RUslpfssk3L8W40NxOeYvJEUPEDzO3g6X3 n+W2X6ZHw41M07RwCUP2+1GaKJ5ns7k+Q4UQjtspmgC83FobKiwFvjLbH4ES193NL204 mOQt1ryvKINhh9bR7hoQgTNz2osXjW7nsN1f9m+mv04eHTtaBYm4DHOpr30SR71ufzGl H8e9nFNUhcm5mh82Pcw6erJIlW7Q2M0+UxWLV+VtsfHvR+P/K8IRBYFNfe3FChiyv94h 2tYA== X-Gm-Message-State: AOAM5301GpzVejKpbeWlKNYdpgMGgXQ7F+ZAfeWvtYS7Ofn9MlpdftqH 6p2eAf8Wgk4TubD99J4IGNo= X-Google-Smtp-Source: ABdhPJwPRub7kMvOD8UgSnAQADBUPOijs5tp4Ni5ZLsZ2eBNz6HAThA27ungI4sO5kCBEcFInLKbkA== X-Received: by 2002:a05:620a:20ce:: with SMTP id f14mr69091qka.367.1627484806532; Wed, 28 Jul 2021 08:06:46 -0700 (PDT) Received: from nuc10 (ec2-35-183-244-153.ca-central-1.compute.amazonaws.com. [35.183.244.153]) by smtp.gmail.com with ESMTPSA id d79sm141995qke.45.2021.07.28.08.06.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 28 Jul 2021 08:06:46 -0700 (PDT) Date: Wed, 28 Jul 2021 08:06:43 -0700 To: John Baldwin Subject: Re: [RFC PATCH] Add a new 'info proc time' subcommand of 'info proc'. Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Rustam Kovhaev via Gdb-patches Reply-To: Rustam Kovhaev Cc: gdb-patches@sourceware.org Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" Hi John, On Wed, Jul 28, 2021 at 08:00:28AM -0700, John Baldwin wrote: > 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? It does not. Linux kernel will need to be patched too, but before sending a kernel RFC patch I wanted to run this proposal by gdb mainteners.