From: 陳韋任 <chenwj@iis.sinica.edu.tw>
To: asmwarrior <asmwarrior@gmail.com>
Cc: gdb@sourceware.org, Xun Xun <xunxun1982@gmail.com>
Subject: Re: gdb crash when I try to print a std::queue (Windows)
Date: Mon, 31 Oct 2011 08:50:00 -0000 [thread overview]
Message-ID: <20111031084035.GA40553@cs.nctu.edu.tw> (raw)
In-Reply-To: <4EAD56D4.5020709@gmail.com>
> So, the conclusion should be:
> This bug is introduced after 20111027, so it is nearly the last week. I hope the developers can find the regression introduced the last week. I'm not familiar with the gdb's source code, but I would like to test for you.
Have you opened a bug report? See http://www.gnu.org/s/gdb/bugs/
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer Systems Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667
next prev parent reply other threads:[~2011-10-31 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-30 13:30 asmwarrior
2011-10-30 18:17 ` asmwarrior
2011-10-31 8:50 ` 陳韋任 [this message]
2011-10-31 8:52 ` asmwarrior
2011-10-31 9:42 ` xunxun
2011-11-01 1:46 ` asmwarrior
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=20111031084035.GA40553@cs.nctu.edu.tw \
--to=chenwj@iis.sinica.edu.tw \
--cc=asmwarrior@gmail.com \
--cc=gdb@sourceware.org \
--cc=xunxun1982@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