From: Michael Snyder <msnyder@vmware.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: question, xmalloc and gdbserver?
Date: Wed, 02 Mar 2011 19:41:00 -0000 [thread overview]
Message-ID: <4D6E9D4D.1070108@vmware.com> (raw)
In-Reply-To: <201103021844.53202.pedro@codesourcery.com>
Pedro Alves wrote:
> On Wednesday 02 March 2011 18:31:28, Michael Snyder wrote:
>> OK, so you're saying that all "legitimate" calls to malloc
>> will be checked?
>
> Yes.
>
Well, here's the one I'm thinking of. It's not clear to me
what to do in case of error. What do you think?
/* Put a stop reply to the stop reply queue. */
static void
queue_stop_reply (ptid_t ptid, struct target_waitstatus *status)
{
struct vstop_notif *new_notif;
new_notif = malloc (sizeof (*new_notif));
new_notif->next = NULL;
new_notif->ptid = ptid;
new_notif->status = *status;
[...]
prev parent reply other threads:[~2011-03-02 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 23:25 Michael Snyder
2011-03-02 9:40 ` Pedro Alves
2011-03-02 18:31 ` Michael Snyder
2011-03-02 18:45 ` Pedro Alves
2011-03-02 19:41 ` Michael Snyder [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=4D6E9D4D.1070108@vmware.com \
--to=msnyder@vmware.com \
--cc=gdb@sourceware.org \
--cc=pedro@codesourcery.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