From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id C52753858D28 for ; Mon, 11 Dec 2023 09:14:11 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C52753858D28 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org C52753858D28 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1702286053; cv=none; b=n4Ea9bFgpe0hDA8JmgYvebpUs5aHB2cVUn/qebjQ2YnE4e4/4eY+I9op1RwFGKcxA4l4sxrmYjn5+IbVSvfNVuW7B6fLsvHyyiKygA754WFZyX8xUeGsbhB0Z7XEZhBsoKfV+FZFL/mrb5n6XRUiBdP5kKxUB7vkVqmSbkAHKys= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1702286053; c=relaxed/simple; bh=nGt+TdCyUm8zEUEm2unw9hen/uGuJro/Dn+ANEkl1jI=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=gOOvEUTHJ1N3tgnQ0c1mjX8YTksQC4f3rTf372ofNjNhiCmfcLZZSPdLPjRRLUYrWkn7Ayg9noBDW6BAVNyZW2Lo547Nzeul1faVKPBvwxcuwM6IAZKxb+tkVs2oFWrpsGW6+QMvxRrIxxORCU0/8u8EWSbWYu14MNSzeFH2GOs= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1702286051; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=D/ELojFi6nIe3+bbZevTk/3wvTApPudcvVkn8G6PypI=; b=clE6CMOgcmN8xj2k2xjat/OWC3YqBkA4xt1SSI9SmHWEzcz4X/3zOUQshW73G2epH3M8Fa SN8YoOgVELSLr3u6y+TZcv0p3XXhgDOeaC+gvwMr4EWUmiR8RNekBZrMwldne5SJFkuqg9 vWd+y27jg0+YvKzUHlwa7TKHCoEWaTY= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-553-Uz70SFIaNmCUH4HdB7TTQQ-1; Mon, 11 Dec 2023 04:14:07 -0500 X-MC-Unique: Uz70SFIaNmCUH4HdB7TTQQ-1 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (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 mimecast-mx02.redhat.com (Postfix) with ESMTPS id A0F90185A782; Mon, 11 Dec 2023 09:14:07 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.141]) by smtp.corp.redhat.com (Postfix) with ESMTPS id C8BF2492BE6; Mon, 11 Dec 2023 09:14:06 +0000 (UTC) From: Florian Weimer To: Abhijit Ray Chaudhury Cc: Abhijit Ray Chaudhury via Libc-help Subject: Re: Does glibc support remote process backtracing References: <87o7ffpn7h.fsf@oldenburg.str.redhat.com> Date: Mon, 11 Dec 2023 10:14:05 +0100 In-Reply-To: (Abhijit Ray Chaudhury's message of "Tue, 28 Nov 2023 13:05:46 +0530") Message-ID: <87bkaxt82q.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.10 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: * Abhijit Ray Chaudhury: > Hi Florian, > > Thanks a lot for replying. I need to do remote stack tracing , for which I am using libunwind-ptrace > . The problem is it does not work on VDSOs . It treats VDSO memory mapping entry in > /proc//maps as a file and tries to open it and subsequently fails. > I tried mailing in libunwind-dev, but it seemed dormant . > > I need a library which works on both arm and x86_64 , do you think elfutils would be a good option > ? The AArch64 vDSO did not have accurate unwinding information in the past. We've got a Fedora bug for this: kernel: vDSO lacks unwind information on aarch64 I don't know if this has been fixed since then. Thanks, Florian