From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: "John S. Yates, Jr." <jyates@netezza.com>, gdb <gdb@sources.redhat.com>
Subject: Re: malloc in inferior
Date: Thu, 29 May 2003 16:42:00 -0000 [thread overview]
Message-ID: <3ED63855.1080706@redhat.com> (raw)
In-Reply-To: <20030529152702.GA10363@nevyn.them.org>
> For some stubs these would be useful; for the stubs I deal with, which
> sit in user space on normal OS's, rather less so. The stub would end
> up calling malloc anyway.
>
> Personally, I'm of the opinion that we should solve this problem by
> changing the definitions: mark strings as ephemeral and let the user
> call malloc or strdup directly if they want something to last.
That wouldn't work. A user needs to be able to cut/paste arbitrary C
source code into the GDB console and have it just work.
Given that most users don't even realize that the malloc is being
called, I think it is working well.
> Or make
> it a set option. I'm not sure how popular that idea would be; anyone
> else have a comment?
A set option, or (discussed previously) allocated lazy fashion.
Andrew
prev parent reply other threads:[~2003-05-29 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 13:51 John S. Yates, Jr.
2003-05-29 15:27 ` Daniel Jacobowitz
2003-05-29 16:00 ` John S. Yates, Jr.
2003-05-29 16:09 ` Daniel Jacobowitz
2003-05-29 17:18 ` John S. Yates, Jr.
2003-05-29 17:24 ` Daniel Jacobowitz
2003-05-29 18:18 ` Andrew Cagney
2003-05-29 18:34 ` Alain Magloire
2003-05-30 13:12 ` John S. Yates, Jr.
[not found] ` <16086.16988.657059.717389@pkoning.dev.equallogic.com>
2003-05-30 13:03 ` John S. Yates, Jr.
2003-05-29 16:42 ` Andrew Cagney [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=3ED63855.1080706@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=jyates@netezza.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).