This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/14845] New: Segmentation fault on "infotracepoints"
- From: "m.lesniewski at samsung dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 15 Nov 2012 14:04:37 +0000
- Subject: [Bug breakpoints/14845] New: Segmentation fault on "infotracepoints"
- Auto-submitted: auto-generated
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.