Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Cedric Roux <sed@free.fr>, "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: "record save" failure
Date: Wed, 22 Jan 2014 03:11:00 -0000	[thread overview]
Message-ID: <m338kgyal3.fsf@redhat.com> (raw)
In-Reply-To: <CANFwon26TA-z0t5TNM4EJFHxA-Sr3cSZhc_-+y_Fn1OzpZ83-A@mail.gmail.com>	(Hui Zhu's message of "Wed, 22 Jan 2014 09:26:12 +0800")

On Tuesday, January 21 2014, Hui Zhu wrote:

> Prec didn't support multithread.

Even so, GDB shouldn't segfault like that.

Cedric, thanks for the report.  Would it be possible for you to test
this with our git HEAD?  Also, if you still find the issue with git
HEAD, could you please file a bug in our bugzilla about this issue?
Thanks.

-- 
Sergio


  reply	other threads:[~2014-01-22  3:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21 13:32 Cedric Roux
2014-01-22  1:26 ` Hui Zhu
2014-01-22  3:11   ` Sergio Durigan Junior [this message]
2014-01-22 15:45     ` Cedric Roux

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=m338kgyal3.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=sed@free.fr \
    --cc=teawater@gmail.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