From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Joel Brobecker <brobecker@adacore.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [patch] Fix cleanup in finish_command
Date: Thu, 20 Jun 2013 15:37:00 -0000 [thread overview]
Message-ID: <A78C989F6D9628469189715575E55B230A96FABA@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <20130620151806.GD4724@adacore.com>
> -----Original Message-----
> From: Joel Brobecker [mailto:brobecker@adacore.com]
> Sent: Thursday, June 20, 2013 5:18 PM
> > BTW I have found the crash happens even with this patch, I haven't found the
> > real cause yet.
>
> Interesting, as I couldn't understand the relationship between
> the backtrace and the patch... You might also be in a situation
> similar to what I faced on Darwin: a correct cleanup fix triggering
> a latent bug; In that situation I found it useful to first git-bisect
> to narrow down the commit that caused the change of behavior, and
> then finish the bug off with valgrind's help.
The bisect will point somewhere into my patch series but it won't be
of much help since most of the patches are just preparing for the
enabling patch at the end of the series.
I have not seen those core files.
Can you point me to a specific test where this happens?
Is there some indication in gdb.log?
Are you using remote or native configuration?
Thanks,
Markus.
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
next prev parent reply other threads:[~2013-06-20 15:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 21:42 Jan Kratochvil
2013-06-20 14:42 ` Jan Kratochvil
2013-06-20 15:26 ` Joel Brobecker
2013-06-20 15:37 ` Metzger, Markus T [this message]
2013-06-20 16:45 ` Jan Kratochvil
2013-06-21 8:14 ` Metzger, Markus T
2013-06-21 8:23 ` Jan Kratochvil
2013-06-21 8:25 ` Metzger, Markus T
2013-07-02 14:50 ` Metzger, Markus T
2013-06-21 12:56 ` Jan Kratochvil
2013-06-20 16:06 ` 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=A78C989F6D9628469189715575E55B230A96FABA@IRSMSX104.ger.corp.intel.com \
--to=markus.t.metzger@intel.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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