public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "andrey.ayupov at intel dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/17437] New: gdb/MI crashes with python-based pretty prints that uses a method call of a class Date: Fri, 26 Sep 2014 22:18:00 -0000 [thread overview] Message-ID: <bug-17437-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17437 Bug ID: 17437 Summary: gdb/MI crashes with python-based pretty prints that uses a method call of a class Product: gdb Version: 7.8 Status: NEW Severity: normal Priority: P2 Component: mi Assignee: unassigned at sourceware dot org Reporter: andrey.ayupov at intel dot com Created attachment 7808 --> https://sourceware.org/bugzilla/attachment.cgi?id=7808&action=edit a synthetic example to reproduce the problem with necessary scripts I was able to create a simple program to reproduce the crash. In fact, originally the bug was found when debugging from Eclipse Kepler SP1, that's why it is the MI interface. In the attachment, you can find the following files: main.cpp - simple program source compile - two commands to build main.cpp gdb_bug_test_pretty_print.cmd - pretty print script mi.cmd - MI commands that would make it crash. They use relative paths so it should just run out of the box if you have all the files in the same directory gdb_bug_test - executable if you happen to be able to run (built on suse11 64 bit), otherwise build using compile script -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-09-26 22:18 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-26 22:18 andrey.ayupov at intel dot com [this message] 2014-10-01 20:17 ` [Bug mi/17437] " andrey.ayupov at intel dot com 2024-01-13 18:50 ` ssbssa at sourceware dot org
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-17437-4717@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).