This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug remote/13978] New: tracepoint condition cannot use string
- From: "teawater at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 13 Apr 2012 05:26:10 +0000
- Subject: [Bug remote/13978] New: tracepoint condition cannot use string
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13978
Bug #: 13978
Summary: tracepoint condition cannot use string
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: remote
AssignedTo: unassigned@sourceware.org
ReportedBy: teawater@gmail.com
Classification: Unclassified
(gdb) trace vfs_read
During symbol reading, cannot get low and high bounds for subprogram DIE at
21765819.
During symbol reading, Child DIE 0x14c29b6 and its abstract origin 0x14c1ee4
have different parents.
Tracepoint 1 at 0xffffffff8117a220: file
/home/teawater/kernel2/linux/fs/read_write.c, line 365.
(gdb) condition 1 (buf[0] == '1')
(gdb) tstart
Unsupported operator (null) (52) in expression.
(gdb) list vfs_read
360 }
361
362 EXPORT_SYMBOL(do_sync_read);
363
364 ssize_t vfs_read(struct file *file, char __user *buf, size_t count,
loff_t *pos)
condition 1 (buf[0] == (int)'1') can handle this issue.
--
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.