Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Orjan Friberg <orjan.friberg@axis.com>
To: gdb-patches@sources.redhat.com
Subject: CRIS port; frame cleanup crash
Date: Mon, 11 Aug 2003 13:30:00 -0000	[thread overview]
Message-ID: <3F379A74.4080508@axis.com> (raw)

After a long overdue update of my gdb cvs tree, I found that something 
broke late March/early April.  I don't quite understand what goes on, 
but it seems to happen the first time a frame allocated by 
deprecated_frame_xmalloc_with_cleanup is freed by do_cleanups (which 
happens in cris_skip_prologue_main).  gdb segfaults on a call to free 
with a pointer to that frame.  The arm-tdep.c file contains the same 
construct of:

   old_chain = make_cleanup (null_cleanup, NULL);
   frame = deprecated_frame_xmalloc_with_cleanup (..., ...)
   <do something with frame>
   do_cleanups (old_chain);

The only thing I found that looked suspicous was that the frame variable 
is allocated by a call to obstack_alloc, but free'd with a "normal" call 
to free.  I would have guessed it should be with obstack_free, but then 
again, my understanding of what happens is limited so far.

Any pointers or suggestions are appreciated.

-- 
Orjan Friberg
Axis Communications



             reply	other threads:[~2003-08-11 13:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-11 13:30 Orjan Friberg [this message]
2003-08-12 15:11 ` Orjan Friberg
2003-08-12 17:36 ` Andrew Cagney
2003-08-13 10:17   ` Orjan Friberg
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=3F379A74.4080508@axis.com \
    --to=orjan.friberg@axis.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