Re: Parsing struct memory?

Path	csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From	Keith Thompson <kst-u@mib.org>
Newsgroups	comp.lang.c
Subject	Re: Parsing struct memory?
Date	Thu, 16 Mar 2017 19:14:59 -0700
Organization	None to speak of
Lines	30
Message-ID	<lnk27ofy3g.fsf@kst-u.example.com> (permalink)
References	<62daf505-60e2-4dd5-b2c7-c619085dd548@googlegroups.com>
Mime-Version	1.0
Content-Type	text/plain; charset=us-ascii
Injection-Info	mx02.eternal-september.org; posting-host="a62e3c498ac96524fc545ef94a9038ec"; logging-data="3057"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+w+GBhVXzoiEg82eWzNPh2"
User-Agent	Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock	sha1:1vC9EQ0MNzU4mSPe6d+3eju3pqQ= sha1:vJfOf0s8/Z5VOukVn2SuicUtw/Q=
Xref	csiph.com comp.lang.c:106310

Show key headers only | View raw

Thiago Adams <thiago.adams@gmail.com> writes:
> Having some struct;
>
> struct {
>   char c;
>   void* p;
>   double d; 
> };
>
> Is it possible to parse it just knowing each type?
> Something similar of var_arg but for structs.
>
> char c = arg(pointer, char);
> void* p = arg(pointer, void*);
> double d = arg(pointer, double);

Not easily or portably.

Once upon a time, I worked on a project that parsed C declarations to
generate C code that would print out the sizes and offsets of all the
members of all the structures in a set of C headers.  The intent was to
use that information to generate code that could access struct members
by name at run time from raw data transmitted to a system with a
possibly different architecture.  (I don't have any of the source code.)

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"

Thread

Parsing struct memory? Thiago Adams <thiago.adams@gmail.com> - 2017-03-16 12:58 -0700
  Re: Parsing struct memory? Thiago Adams <thiago.adams@gmail.com> - 2017-03-16 13:21 -0700
    Re: Parsing struct memory? Ian Collins <ian-news@hotmail.com> - 2017-03-17 11:16 +1300
      Re: Parsing struct memory? James Kuyper <jameskuyper@verizon.net> - 2017-03-16 22:09 -0400
        Re: Parsing struct memory? Ian Collins <ian-news@hotmail.com> - 2017-03-17 15:23 +1300
        Re: Parsing struct memory? David Brown <david.brown@hesbynett.no> - 2017-03-17 10:11 +0100
          Re: Parsing struct memory? "James R. Kuyper" <jameskuyper@verizon.net> - 2017-03-17 11:35 -0400
    Re: Parsing struct memory? gordonb.7zilv@burditt.org (Gordon Burditt) - 2017-03-16 20:17 -0500
      Re: Parsing struct memory? James Kuyper <jameskuyper@verizon.net> - 2017-03-16 21:56 -0400
  Re: Parsing struct memory? supercat@casperkitty.com - 2017-03-16 13:51 -0700
    Re: Parsing struct memory? Lowell Gilbert <lgusenet@be-well.ilk.org> - 2017-03-16 19:39 -0400
      Re: Parsing struct memory? BartC <bc@freeuk.com> - 2017-03-17 12:16 +0000
      Re: Parsing struct memory? "Peter \"Shaggy\" Haywood" <phaywood@alphalink.com.au> - 2017-03-24 18:06 +1100
        Re: Parsing struct memory? supercat@casperkitty.com - 2017-03-24 14:35 -0700
  Re: Parsing struct memory? Keith Thompson <kst-u@mib.org> - 2017-03-16 19:14 -0700
    Re: Parsing struct memory? scott@slp53.sl.home (Scott Lurndal) - 2017-03-17 12:45 +0000
  Re: Parsing struct memory? scott@slp53.sl.home (Scott Lurndal) - 2017-03-17 12:41 +0000
  Re: Parsing struct memory? Thiago Adams <thiago.adams@gmail.com> - 2017-03-17 08:17 -0700
  Re: Parsing struct memory? Thiago Adams <thiago.adams@gmail.com> - 2017-03-20 05:07 -0700

csiph-web