From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 8AtsC3CuQ2p5RR8AWB0awg (envelope-from ) for ; Tue, 30 Jun 2026 07:54:24 -0400 Authentication-Results: simark.ca; dkim=pass (1024-bit key; unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=hy6B9ULy; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 119B71E024; Tue, 30 Jun 2026 07:54:24 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_SBL_CSS autolearn=ham autolearn_force=no version=4.0.1 Received: from vm01.sourceware.org (vm01.sourceware.org [IPv6:2620:52:6:3111::32]) (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 51C241E024 for ; Tue, 30 Jun 2026 07:54:23 -0400 (EDT) Received: from vm01.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 6AF9E4BA2E3C for ; Tue, 30 Jun 2026 11:54:22 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6AF9E4BA2E3C Authentication-Results: sourceware.org; dkim=pass (1024-bit key, unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=hy6B9ULy Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTP id 7E38E4BA2E0E for ; Tue, 30 Jun 2026 11:53:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 7E38E4BA2E0E Authentication-Results: sourceware.org; dmarc=pass (p=quarantine 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 7E38E4BA2E0E Authentication-Results: sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1782820438; cv=none; b=abVBSmYUcq+RryqrhbIGJ55r/d2kpCgmM3ZtL9gHLbW30GJRX1B2f+z9Z6iqkaMb+eFMVtkASN3Cb4g2kkzzmp72psjHVaGpKN3Kz/vPyvNc6iLwIJNfn0kLbZpDJFP1oelQzZoTG7dfsWYMU4lW0tqzHHM2rMRxUiGY4nhgED0= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1782820438; c=relaxed/simple; bh=VqThLb2ee4V2UnGqrtPEHeCiYRmzoAVRHzvgZ/2Pcu0=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=d4Al5Lp6sG6TbRM4FqGOL0mISzEwuzZEHHM8DJL1UROQp7adduLp90Wu6tBhJbJO0w/cFinLSkqWRuqABER7sDTVTPbqEOshfNO+M/kJ3RgfHDPN4VWtqpX8UEO3UpsFY69wQPH2kbAZKkutLV26JNes98Ubz0m5fPhjekWVQHQ= ARC-Authentication-Results: i=1; sourceware.org; dkim=pass (1024-bit key, unprotected) header.d=redhat.com header.i=@redhat.com header.a=rsa-sha256 header.s=mimecast20190719 header.b=hy6B9ULy DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7E38E4BA2E0E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1782820438; 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=VqThLb2ee4V2UnGqrtPEHeCiYRmzoAVRHzvgZ/2Pcu0=; b=hy6B9ULyW1BUN4NdftLSgIPzCa0Qvmot19ZEvJ6tVvIY8I2RGuFqN8OKwQueGrjcFUnnAl SxuyNiMBnmTBK1VdaBB6JoMfqHAme0aw5OrW5XPiV8Nf4mCPTaUSoOnFofpFyHdE7AixCw 5NedZTUeVR2qxBp84qc55JXVJUGk/OU= Received: from mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-629-D2hPRENzNsGJkHHf-NYt8w-1; Tue, 30 Jun 2026 07:53:53 -0400 X-MC-Unique: D2hPRENzNsGJkHHf-NYt8w-1 X-Mimecast-MFC-AGG-ID: D2hPRENzNsGJkHHf-NYt8w_1782820431 Received: from mx-prod-int-10.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-10.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.95]) (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 mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 3E62B1954ADE; Tue, 30 Jun 2026 11:53:51 +0000 (UTC) Received: from fweimer-oldenburg.csb.redhat.com (unknown [10.44.48.121]) by mx-prod-int-10.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 78DC936927; Tue, 30 Jun 2026 11:53:43 +0000 (UTC) From: Florian Weimer To: Wilco Dijkstra Cc: Yury Khrustalev , Muhammad Kamran , "gdb-patches@sourceware.org" , Andrew Burgess , Thiago Jung Bauermann , Adhemerval Zanella Netto , Carlos O'Donell Subject: Re: [PATCH v2 1/1] gdb: Preserve IFUNC marker when finding inferior functions In-Reply-To: (Wilco Dijkstra's message of "Tue, 30 Jun 2026 09:42:54 +0000") References: <20260625152036.6149-1-muhammad.kamran@arm.com> <20260625152036.6149-2-muhammad.kamran@arm.com> Date: Tue, 30 Jun 2026 13:53:40 +0200 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.6 on 10.30.177.95 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: ji48NsQQdxEl42ZnOyosZ_Oa1S2zRvTZvOHVWaChUo8_1782820431 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces~public-inbox=simark.ca@sourceware.org * Wilco Dijkstra: > Hi, > >> Perhaps we should add an alias to __libc_malloc (and other malloc >> functions that GDB needs) for GDB, something like `__gdb_malloc` >> that would become Glibc's ABI for GDB? This is not ideal of course >> as GDB would need to look for this new symbol and than still fallback >> to 'malloc' to support other non-Glibc runtimes. > > If the debugger just randomly changes malloc state, it's impossible to > debug memory or pointer issues... > > So I don't believe it should use malloc or a different helper. String > arguments can be placed on the stack just like any other arguments > (within a reasonable limit - anything too large could simply be refused > just like a call with 1M arguments). I think for literals, most uses expect different life-times. Does GDB ever free the copy of the literal? Thanks, Florian