From: Orjan Friberg <orjan.friberg@axis.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: CRIS port; frame cleanup crash
Date: Wed, 13 Aug 2003 10:17:00 -0000 [thread overview]
Message-ID: <3F3A102C.3080403@axis.com> (raw)
In-Reply-To: <3F392591.4050409@redhat.com>
Andrew Cagney wrote:
>
> Er, that points at a bug:
>
> struct frame_info *
> deprecated_frame_xmalloc (void)
> {
> struct frame_info *frame = FRAME_OBSTACK_ZALLOC (struct frame_info);
> frame->this_id.p = 1;
> return frame;
> }
>
> shouldn't be allocated from the frame obstack pool. I'll commit a fix.
Thanks a lot; it works fine now.
--
Orjan Friberg
Axis Communications
next prev parent reply other threads:[~2003-08-13 10:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 13:30 Orjan Friberg
2003-08-12 15:11 ` Orjan Friberg
2003-08-12 17:36 ` Andrew Cagney
2003-08-13 10:17 ` Orjan Friberg [this message]
2004-02-12 18:59 ` Orjan Friberg
2004-02-12 20:06 ` Andrew Cagney
2004-02-14 13:38 ` Orjan Friberg
2004-02-14 14:52 ` Andrew Cagney
2004-02-15 17:41 ` Orjan Friberg
2004-02-16 18:19 ` Orjan Friberg
2004-02-16 18:43 ` Andrew Cagney
2004-02-18 17:06 ` Orjan Friberg
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=3F3A102C.3080403@axis.com \
--to=orjan.friberg@axis.com \
--cc=ac131313@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