From: Tom Tromey <tromey@redhat.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "'Joel Brobecker'" <brobecker@adacore.com>,
"'gdb-patches\@sourceware.org'"
<gdb-patches@sourceware.org>
Subject: Re: [Python] Segfault when clearing pspace
Date: Thu, 16 Dec 2010 21:26:00 -0000 [thread overview]
Message-ID: <m3mxo5if3s.fsf@fleche.redhat.com> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC572EA2C1DF@EUSAACMS0703.eamcs.ericsson.se> (Marc Khouzam's message of "Wed, 15 Dec 2010 10:56:46 -0500")
>>>>> "Marc" == Marc Khouzam <marc.khouzam@ericsson.com> writes:
Marc> The existing FIXME comment about how to get the arch seems to
Marc> confirm that something should be fixed there.
Marc> Below the patch is a session that shows how to reproduce
Marc> the crash.
Marc> What do you think?
Please remove the FIXME comment.
This is ok with that change plus a ChangeLog entry.
thanks
Tom
next prev parent reply other threads:[~2010-12-16 21:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-04 19:11 Assertion failure because of missing inferior Marc Khouzam
2010-12-07 18:54 ` Tom Tromey
2010-12-08 1:38 ` Marc Khouzam
2010-12-10 19:59 ` Tom Tromey
2010-12-10 20:21 ` Marc Khouzam
2010-12-10 21:01 ` Marc Khouzam
2010-12-10 21:38 ` Marc Khouzam
2010-12-14 14:50 ` Tom Tromey
2010-12-14 15:04 ` Joel Brobecker
2010-12-14 15:31 ` Pedro Alves
2010-12-15 5:12 ` Joel Brobecker
2010-12-14 20:00 ` Marc Khouzam
2010-12-15 15:57 ` [Python] Segfault when clearing pspace (was: RE: Assertion failure because of missing inferior) Marc Khouzam
2010-12-16 21:26 ` Tom Tromey [this message]
2010-12-18 2:13 ` [Python] Segfault when clearing pspace Marc Khouzam
2010-12-18 2:19 ` Assertion failure because of missing inferior Marc Khouzam
2010-12-14 14:49 ` Tom Tromey
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=m3mxo5if3s.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.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