public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "m.lesniewski at samsung dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/14845] New: Segmentation fault on "info tracepoints" Date: Thu, 15 Nov 2012 14:04:00 -0000 [thread overview] Message-ID: <bug-14845-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14845 Bug #: 14845 Summary: Segmentation fault on "info tracepoints" Product: gdb Version: 7.5 Status: NEW Severity: normal Priority: P2 Component: breakpoints AssignedTo: unassigned@sourceware.org ReportedBy: m.lesniewski@samsung.com Classification: Unclassified Created attachment 6739 --> http://sourceware.org/bugzilla/attachment.cgi?id=6739 Example program, library and test script The following steps cause a segmentation fault to occur in gdb: 1. The debugged process loads a library dynamically (using dlload); 2. The user sets a tracepoint in a function in the library and starts the trace experiment; 3. The debugged process unloads the library (dlclose); 4. The user stops the trace; 5. The user issues the tfind command until no more traceframes are found 5. The user issues the "info tracepoints" The attached archive contains a simple example program and scripts, which allow to reproduce the problem. To run the scenario launch run-test.sh. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-11-15 14:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-15 14:04 m.lesniewski at samsung dot com [this message] 2012-11-15 14:05 ` [Bug breakpoints/14845] " m.lesniewski at samsung dot com 2012-11-15 14:06 ` m.lesniewski at samsung dot com 2012-11-15 14:39 ` qiyao at gcc dot gnu.org 2012-11-15 14:57 ` palves at redhat dot com 2012-11-15 15:34 ` m.lesniewski at samsung dot com 2012-11-15 15:35 ` m.lesniewski at samsung dot com
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-14845-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).