From owner-freebsd-dtrace@freebsd.org Mon Mar 2 16:58:28 2020 Return-Path: Delivered-To: freebsd-dtrace@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6F4A7253C13 for ; Mon, 2 Mar 2020 16:58:28 +0000 (UTC) (envelope-from kamalpr@gmail.com) Received: from mail-pl1-x641.google.com (mail-pl1-x641.google.com [IPv6:2607:f8b0:4864:20::641]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48WRDM4ZkBz4B4b; Mon, 2 Mar 2020 16:58:27 +0000 (UTC) (envelope-from kamalpr@gmail.com) Received: by mail-pl1-x641.google.com with SMTP id x17so252366plm.10; Mon, 02 Mar 2020 08:58:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=MktKqbG3QTmUQPWeRvWCIbxL4JznJZTAmJIy6FTJo4s=; b=qE4Z74+80eCg77d0ZXBwkzWD4xBfYJjvbhTFHz4F8USWdnVZlrZj5gFSsY5lU6kEEs AlG3srTUoXoaHkK7sO6lfc7Tm9OKsFNWj/e1ExY698CRachIWbfOnMdbYQ3DmxqkVAi4 gMkU+d6aFsgAx0W+BQsoRwZi1R6zfYN6p1/6c06Y3xALj69D0vVfmhC7GI5S32x5mKwE azz4IhxOizDTp2C/jYVYZ5i/mFF5qIojquCQ6W97SSXIS6FQkeu61JWQHXi+vhHuAVg6 Ur8OizvifiPJi4BL3KsMQtpMt66BnEZocthsUuT8mJDnWvQD1ZahWo5MIJ4fgoKArMVi qMBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=MktKqbG3QTmUQPWeRvWCIbxL4JznJZTAmJIy6FTJo4s=; b=KfZEDw1Uz5JVH3rB4J5yVx0c3rTNtEYYs7UesA/Jyoabv1/jyN+bf4apV9O5C4Adi4 7fpC3yl77JfUZoerr87oofzMmplJMOHvsT2Luvb2zvWGH9Uuv4b1idIzqCiSleoGuLmW e89pg8YVTJGXXpD4tyUF5XiaNzZZgoYs+XWY03Cy7UppMpUSbk6jNWCPDaIrMI8CGRX0 5jgq9aAlIn52Z9Q4LHUPmhXBsYvGDVjKp/jKbrlPLp/RSiwJ4lxgufwOHGwyNthA2UWM R0OQ15JLind09wztRuUyBmt+mlnOynl4YbrvNNovLm5RoIPXUWxGgCxCE6x5xh6FS4BQ gTWg== X-Gm-Message-State: ANhLgQ34hSJWmCfTQzKzBGWKthD2SzZ0K0C/3Oq76hzkk9LHThPbHuAK z0ZKdCDAa0SkrT5Vk/zZvLimUJYpgw== X-Google-Smtp-Source: ADFU+vuhrWe5rP+S4sem4gvO6QyUzYdE71IHLxxtseZph6NkTAZl9pyNr5MrEgnVNobD4hbxHNf5xQ== X-Received: by 2002:a17:90a:c687:: with SMTP id n7mr464139pjt.155.1583168305629; Mon, 02 Mar 2020 08:58:25 -0800 (PST) Received: from [192.168.1.3] ([122.179.30.234]) by smtp.gmail.com with ESMTPSA id q9sm21464134pgs.89.2020.03.02.08.58.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Mar 2020 08:58:24 -0800 (PST) From: Kamal Prasad Message-Id: <2D6C721A-C868-4D4F-90CD-9D57BC783ADF@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: set argument Date: Mon, 2 Mar 2020 22:32:31 +0530 In-Reply-To: <20200302161350.GB26104@spy> Cc: freebsd-dtrace@freebsd.org To: Mark Johnston References: <20200302161350.GB26104@spy> X-Mailer: Apple Mail (2.3273) X-Rspamd-Queue-Id: 48WRDM4ZkBz4B4b X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-5.99 / 15.00]; NEURAL_HAM_MEDIUM(-0.99)[-0.989,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-dtrace@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "A discussion list for developers working on DTrace in FreeBSD." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Mar 2020 16:58:28 -0000 In userspace. Where do you provide information so that dtrace can = automatically see sys/net/route.h structs like struct rtentry? I want to add some more files so that their structs are also = automatically seen by dtrace. > On Mar 2, 2020, at 9:43 PM, Mark Johnston wrote: >=20 > On Mon, Mar 02, 2020 at 03:33:57PM +0530, Kamal R. Prasad wrote: >> hello, >>=20 >> How does dtrace access the argument type declarations when we define = a new >> SDT? eg:- I define an SDT that has arg0 as (struct mystrust*) >>=20 >> I have defined in my proprietary header file >> --------------- >> typedef struct abc { >> int a; >> int b; >> int c; >> }; >> typedef struct def { >> int d; >> int e; >> int f; >> }; >>=20 >> typedef struct mystrust { >> struct abc* myarg1; >> struct def* myarg2 >> }; >> --------------- >>=20 >> I want my probe to be able to access the typedeffor struct abc and = struct >> def. >=20 > Is this in the kernel or userspace? We automatically build the kernel > with CTF info included, so dtrace should be able to see the structure > definitions automatically. > _______________________________________________ > freebsd-dtrace@freebsd.org mailing = list > https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace = > To unsubscribe, send any mail to = "freebsd-dtrace-unsubscribe@freebsd.org = "