From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id CGygMXx0Kma9wTsAWB0awg (envelope-from ) for ; Thu, 25 Apr 2024 11:19:24 -0400 Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=WQ5RtKkh; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id C714B1E0C0; Thu, 25 Apr 2024 11:19:24 -0400 (EDT) Received: from server2.sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id B1F9F1E092 for ; Thu, 25 Apr 2024 11:19:22 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 45F45385840E for ; Thu, 25 Apr 2024 15:19:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 45F45385840E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1714058362; bh=KhoTHtuZsdtaotSvwkBl0ctE4uspKk+p6beKwJgNXRk=; h=Date:To:Cc:In-Reply-To:Subject:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=WQ5RtKkhm7rBBgUIumuW826yhxEyo+IlaMNkcmLyluMOBglZ2Uc6EHcDEcPPY1Up3 BM9xz4xhrPOJXEejqcQaiXrV6N5gr1gg3b0MSFinsyq1eDUQY26lPgJaw03ybpc+4c ryGN1GnQgLI0tmB9dPb+8rJxr1OxQ5g8n6WFx1CU= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 7C6AF3858D38 for ; Thu, 25 Apr 2024 15:18:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 7C6AF3858D38 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 7C6AF3858D38 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1714058321; cv=none; b=rmI8i36Vk/CTXKTd4ctL21OMiuTXrnlpet3deWGSTDqieS3fyUe76PpwxjEqGgJRt7BDWnvjfxTp03KnKzQoDxISeMtqE1k9dpdg33fDfrsFnciyEpldyMugaqGFmJWr4GqiX90RwjYXCEEylmBOAlDHNSRfsGgJjXj271nKLAk= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1714058321; c=relaxed/simple; bh=BTbdcRUsL8BqVfC5o9zzgvg+Ms+Xc4JiXqwrJXA83xo=; h=DKIM-Signature:Date:Message-Id:From:To:Subject; b=KNz3YsH46O6xoh4ssHY55pibTaJIhCiMhMRBiNKWymnOBX7fbGu8aDMQCrJwsgKDHGXYfK2Px57PEcYrRlQICFegNhZIIJzuzpSooDd+cZr8aBgIZFS51B3WkyxTq4GJmUBmyTqe2/g/uJeGQylm03cDjVZaeSCLbGRv0AMPsiA= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s00rm-00031D-C1; Thu, 25 Apr 2024 11:18:30 -0400 Date: Thu, 25 Apr 2024 18:17:56 +0300 Message-Id: <86frv91nff.fsf@gnu.org> To: Luis Machado Cc: gdb@sourceware.org, tom@tromey.com, nd@arm.com In-Reply-To: <1575098d-c3de-4a87-9868-7ff5e5994312@arm.com> (message from Luis Machado on Thu, 25 Apr 2024 11:13:29 +0100) Subject: Re: Debugging with GDB and ASLR References: <86v8452237.fsf@gnu.org> <1575098d-c3de-4a87-9868-7ff5e5994312@arm.com> X-Spam-Status: No, score=-0.1 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Eli Zaretskii via Gdb Reply-To: Eli Zaretskii Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" > Date: Thu, 25 Apr 2024 11:13:29 +0100 > Cc: nd > From: Luis Machado > > On 4/25/24 11:01, Eli Zaretskii via Gdb wrote: > > Hi, > > > > It is well known that ASLR can get in the way of debugging some > > problems because the addresses of data change between runs, and so > > what you have learned from one debugging session cannot always be > > safely used in another session, when ASLR is in effect. > > > > I'm told that GDB disables ASLR, at least on GNU/Linux, for that > > reason. If that is true, could someone please point me to the code > > which achieves that? Also, is this done on other systems as well, and > > specifically on MS-Windows when debugging native Windows programs? > > > > TIA > > On Linux, it does so through the personality function in gdb/nat/linux-personality.c. > > I heard there were issues with disabling ASLR for Windows, but we seem to try to do > it in gdb/nat/windows-nat.c:create_process_wrapper. Maybe the call to UpdateProcThreadAttribute > attempts to do it? Right, thanks.