Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Pedro Alves'" <pedro@codesourcery.com>
Cc: "'Joel Brobecker'" <brobecker@adacore.com>, <gdb-patches@sourceware.org>
Subject: RE: [BUG] Quit and "(running)" problem
Date: Fri, 16 Jan 2009 08:55:00 -0000	[thread overview]
Message-ID: <000001c977b8$061f6b60$125e4220$@u-strasbg.fr> (raw)
In-Reply-To: <200901152215.00564.pedro@codesourcery.com>

  I can confirm that your patch fixed the simple
test case that I submitted in PR9747.
As such I of course 

  Reading the patch, I was wondering about the
utility of the old_chain cleanup in fetch_inferior_event
function. But this is probably due to my
lack of comprehension of the cleanup chain mechanisms.

  Is it really possible to reach
  do_cleanups (old_chain)
with something else that old_chain
as the top item on the cleanup list?
  I thought that all the cleanups where stored
as local variables, so that all cleanups
that were set in functions called while running any
code called from within the fetch_inferior_event
would be invalid data anyhow at that point,
as the stack might have been overwritten by calls to other functions.


Pierre Muller
Pascal language support maintainer for GDB




  reply	other threads:[~2009-01-16  8:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15 12:40 Pierre Muller
2009-01-15 13:59 ` Joel Brobecker
2009-01-15 16:03   ` Pierre Muller
2009-01-15 22:15     ` Pedro Alves
2009-01-16  8:55       ` Pierre Muller [this message]
2009-01-16 15:13         ` Pedro Alves
2009-01-16 15:39           ` Pierre Muller
2009-01-15 14:42 ` Pedro Alves

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='000001c977b8$061f6b60$125e4220$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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