From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id v+UeB9GpY2AfdwAAWB0awg (envelope-from ) for ; Tue, 30 Mar 2021 18:44:33 -0400 Received: by simark.ca (Postfix, from userid 112) id 101271EE0E; Tue, 30 Mar 2021 18:44:33 -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 5D1D41E01F for ; Tue, 30 Mar 2021 18:44:32 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 083173858012; Tue, 30 Mar 2021 22:44:32 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 083173858012 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1617144272; bh=05hIyMMoEhLp0QzWAyaiLoXiAJvRL02Sp2z//HGPQaY=; h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=oDLZFnGpXWETJtvAsacnPv5bkGyVQl0ZhJrH05XwbissSOWC09nJrC47BOkDms/+7 b1hCnMwo06VSrw3NC9XERoSoqm3il9ERVcMNcZPtIn/0A/8zoAkfXLdExqduIZd/63 X/mmvj3V4yuQ2lAO6J54TPM50FwVHjrr9smerJ/M= Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) by sourceware.org (Postfix) with ESMTPS id A39313858012 for ; Tue, 30 Mar 2021 22:44:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org A39313858012 Received: by mail-pj1-x102a.google.com with SMTP id kk2-20020a17090b4a02b02900c777aa746fso206489pjb.3 for ; Tue, 30 Mar 2021 15:44:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YTSbIJtvLazEMyoVmRDWWqsZju+WbjC9bt2VZQxR+b0=; b=FCVDUmV9wmzCcgXtuxo4MizIP3m5vwoaTODn0GZ2YvxDPcYdWDJ5dv6WeylvLSOq9o RHSEBQ4xAkKyiDvpacgHwMqXWiURvQvlsA//A4xVHZAxUCE6K1HFHUulaAVIS4QoRuvD f+XsJG0TSon3LFNkQxW/NY3zsU7a9qKrk2Bw1C4WonRQnv0T/Kmq2ALmU21ksehQ6RJs GOv8vq4kOF5uTd4StsIwHajnjpuajDqabjnTZUlFPoBoHRpCzQ5mz2M/jp5rFHLb+Snf vIQmif74/2A95GNw2/69weFou/q5/IJpn4hBGZeBolTXHKh2L5BCpgCThmH8wW6jf8DU 0jEQ== X-Gm-Message-State: AOAM531qT/UsE7Kapb6fW+7Ij7cN5CU8TgXeNSjTSg8ODKWvwQfxrqaj dV2QEBCy6IwSAxwFCeaGx6gRkzbXgq3aNaLR6wk= X-Google-Smtp-Source: ABdhPJzc2K9rxeznxLO/vOZCuTajwEiYBvkMXportcNYC2wNvhYbajbYRLURLgogdpVsVOwrc+bsNxw0vEAph6ztK+I= X-Received: by 2002:a17:90b:1490:: with SMTP id js16mr489559pjb.131.1617144268818; Tue, 30 Mar 2021 15:44:28 -0700 (PDT) MIME-Version: 1.0 References: <6b00bbbe-1400-7f11-bdcf-811595bf8e31@polymtl.ca> In-Reply-To: Date: Tue, 30 Mar 2021 15:44:17 -0700 Message-ID: Subject: Re: Remote query for structure layout To: Simon Marchi Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: David Blaikie via Gdb Reply-To: David Blaikie Cc: Tim Newsome , gdb Errors-To: gdb-bounces@sourceware.org Sender: "Gdb" On Tue, Mar 30, 2021 at 3:38 PM Simon Marchi wrote: > On 2021-03-30 6:03 p.m., David Blaikie wrote:> > > Perhaps - though I was thinking actually hardcoded in the compiler - > since it's the one that chooses/knows the layout, it's not (presumably) > using any code it reads from a header, etc, in user code to define the > layout. > > Is it really the compiler that decides this layout? My understanding is > that this is decided by the FreeRTOS code. > > Having used FreeRTOS a few times, my understanding is that it's > basically a big library, the compiler doesn't really know about it. For > all it knows, you are compiling a bare metal program that happens to > implement a task system. > Ah, sorry, my misunderstanding then - knew nothing about it. Sorry about that. If it's "just" some user-code, is there a variable of the desired type being declared around the function call?