From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Berlin <dberlin@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Add support for tracking/evaluating dwarf2 location expressions
Date: Fri, 06 Apr 2001 11:53:00 -0000 [thread overview]
Message-ID: <3ACE108C.725903B7@cygnus.com> (raw)
In-Reply-To: <m23dbu8x93.fsf@dynamic-addr-83-177.resnet.rochester.edu>
> > value_ptr stack[64];
> > Is there a constant for this? A quick glance at decode_locdesc() and it
> > has the same hardwired constant.
> Nobody has ever produced location expressions that need more.
The problem typically isn't with what people are doing intentionally but
rather unintentionally. The code opens the way for an input file to
cause gdb to overflow a buffer and trash its stack.
Since we're trying to lessen the likelyhood of GDB corrupting its stack
and dumping core, I think the code should include some sort of stack
range check.
Andrew
next prev parent reply other threads:[~2001-04-06 11:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-30 11:11 Daniel Berlin
2001-03-30 15:36 ` Andrew Cagney
2001-03-30 18:53 ` Daniel Berlin
2001-04-06 11:53 ` Andrew Cagney [this message]
2001-04-06 12:10 ` Daniel Berlin
2001-04-06 12:36 ` Kevin Buettner
2001-04-06 23:18 ` [PATCH] Add support for tracking/evaluating dwarf2 locationexpressions Daniel Berlin
2001-05-21 14:46 ` [PATCH] Add support for tracking/evaluating dwarf2 location expressions Jim Blandy
2001-05-21 18:49 ` Daniel Berlin
2001-05-22 12:46 ` Jim Blandy
2001-05-22 13:51 ` Daniel Berlin
2001-05-22 23:14 ` Jim Blandy
2001-05-23 8:51 ` Daniel Berlin
2001-05-23 11:53 ` Daniel Berlin
2001-05-23 21:53 ` Jim Blandy
2001-05-23 22:56 ` Daniel Berlin
2001-06-06 9:07 ` Andrew Cagney
2001-06-06 9:46 ` Daniel Berlin
2001-06-07 7:29 ` Andrew Cagney
2001-03-30 13:49 David Taylor
2001-03-30 14:42 ` Daniel Berlin
2001-03-30 15:14 ` Andrew Cagney
2001-03-30 18:44 ` Daniel Berlin
2001-03-30 15:23 ` Elena Zannoni
2001-03-30 15:24 ` Andrew Cagney
2001-03-30 18:46 ` Daniel Berlin
2001-04-06 12:02 ` Andrew Cagney
2001-04-06 12:40 ` Daniel Berlin
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=3ACE108C.725903B7@cygnus.com \
--to=ac131313@cygnus.com \
--cc=dberlin@redhat.com \
--cc=gdb-patches@sources.redhat.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