From: Tom Tromey <tom@tromey.com>
To: Tom Tromey <tom@tromey.com>
Cc: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix malloc allocation size sanity check
Date: Wed, 12 Aug 2020 13:32:01 -0600 [thread overview]
Message-ID: <87lfijhd8u.fsf@tromey.com> (raw)
In-Reply-To: <87pn7vhd9o.fsf@tromey.com> (Tom Tromey's message of "Wed, 12 Aug 2020 13:31:31 -0600")
Tom> main_type::length is a ULONGEST, so maybe that would be better?
Oops, I mean type::length.
Tom
next prev parent reply other threads:[~2020-08-12 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 19:17 Luis Machado
2020-08-12 19:31 ` Tom Tromey
2020-08-12 19:32 ` Tom Tromey [this message]
2020-08-12 19:46 ` Luis Machado
2020-08-17 11:01 ` Gary Benson
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=87lfijhd8u.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
/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