public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dtaylor at emc dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/17109] gdb 7.7 crashes when issuing mi command: -trace-frame-collected Date: Tue, 15 Jul 2014 20:29:00 -0000 [thread overview] Message-ID: <bug-17109-4717-5VPVMt3CuO@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17109-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17109 --- Comment #3 from David Taylor <dtaylor at emc dot com> --- In mi_cmd_trace_frame_collected we find the line: tinfo = get_traceframe_info (); Now, get_traceframe_info can legitimately return NULL. And, since this is a remote target to a stub that does not support the qXfer:traceframe-info:read message, it DOES return NULL. Later in the function we find the line: for (i = 0; VEC_iterate (int, tinfo->tvars, i, tvar); i++) There is no guard to check that tinfo is non NULL, so this produces the core dump. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2014-07-15 20:29 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-02 22:26 [Bug mi/17109] New: " hochby at emc dot com 2014-07-03 1:59 ` [Bug mi/17109] " qiyao at gcc dot gnu.org 2014-07-10 23:36 ` dtaylor at emc dot com 2014-07-15 20:29 ` dtaylor at emc dot com [this message]
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=bug-17109-4717-5VPVMt3CuO@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).