From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: "Cuthbertson, Reva D." <reva_cuthbertson@hp.com>, gdb@sources.redhat.com
Subject: Re: Is it possible to overflow baton->size in dwarf_mark_symbols_computed() in dwarf2read.c?
Date: Mon, 16 May 2005 20:28:00 -0000 [thread overview]
Message-ID: <vt27jhy6htb.fsf@zenia.home> (raw)
In-Reply-To: <20050513153945.GA9246@nevyn.them.org>
Daniel Jacobowitz <drow@false.org> writes:
> No. It should saturate instead; it only needs to be longer than any
> supported location list/expression, and 64k is entirely reasonable for
> that. Int would waste a lot of memory.
Both those structures are twelve bytes long anyway. Their 'size'
fields are followed by two bytes of padding on IA-32.
next prev parent reply other threads:[~2005-05-16 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 15:37 Cuthbertson, Reva D.
2005-05-13 15:40 ` Daniel Jacobowitz
2005-05-16 20:28 ` Jim Blandy [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-13 16:00 Cuthbertson, Reva D.
2005-05-13 15:19 Cuthbertson, Reva D.
2005-05-13 15:25 ` Daniel Jacobowitz
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=vt27jhy6htb.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=reva_cuthbertson@hp.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).