From: "Hannes Domani via gdb-patches" <gdb-patches@sourceware.org>
To: Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] Add type for $_tlb->process_environment_block->process_parameters
Date: Thu, 16 Jan 2020 20:23:00 -0000 [thread overview]
Message-ID: <141361473.21346688.1579205935219@mail.yahoo.com> (raw)
In-Reply-To: <dcbc3686-0baa-22cd-1122-55c659932f73@simark.ca>
Am Donnerstag, 16. Januar 2020, 20:56:45 MEZ hat Simon Marchi <simark@simark.ca> Folgendes geschrieben:
> > @@ -219,6 +227,58 @@ windows_get_tlb_type (struct gdbarch *gdbarch)
> > NULL);
> > TYPE_TARGET_TYPE (peb_ldr_ptr_type) = peb_ldr_type;
> >
> > + /* struct UNICODE_STRING */
> > + uni_str_type = arch_composite_type (gdbarch, xstrdup ("unicode_string"),
> > + TYPE_CODE_STRUCT);
> > +
> > + append_composite_type_field (uni_str_type, "length", word_type);
> > + append_composite_type_field (uni_str_type, "maximum_length", word_type);
> > + append_composite_type_field_aligned (uni_str_type, "buffer",
> > + wchar_ptr_type,
> > + TYPE_LENGTH (wchar_ptr_type));
> > +
> > + /* struct _RTL_USER_PROCESS_PARAMETERS */
> > + rupp_type = arch_composite_type (gdbarch,
> > + xstrdup ("rtl_user_process_parameters"),
> > + TYPE_CODE_STRUCT);
>
>
> I'm pretty sure it would be fine to not xstrdup the names. gdbarch types are never
> freed (we don't delete gdbarch objects), and even then they don't assume that their
> name has been dynamically allocated, they would not try to free it.
Pushed with this change, thanks.
Hannes
prev parent reply other threads:[~2020-01-16 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200116180050.15777-1-ssbssa.ref@yahoo.de>
2020-01-16 18:14 ` Hannes Domani via gdb-patches
2020-01-16 20:19 ` Simon Marchi
2020-01-16 20:23 ` Hannes Domani via gdb-patches [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=141361473.21346688.1579205935219@mail.yahoo.com \
--to=gdb-patches@sourceware.org \
--cc=ssbssa@yahoo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox