This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/18263] In tty tapset, driver_name can be null, causing a script to fail when probing tty.write or tty.read
- From: "dsmith at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 14 Apr 2015 19:23:28 +0000
- Subject: [Bug tapsets/18263] In tty tapset, driver_name can be null, causing a script to fail when probing tty.write or tty.read
- Auto-submitted: auto-generated
- References: <bug-18263-6586 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18263
David Smith <dsmith at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #8248|0 |1
is obsolete| |
--- Comment #4 from David Smith <dsmith at redhat dot com> ---
Created attachment 8249
--> https://sourceware.org/bugzilla/attachment.cgi?id=8249&action=edit
kernel_string_quoted patch
Here's a better patch that replaces all use of kernel_string() with
kernel_string_quoted() in tty.stp. The problem with kernel_string3() is that it
if returned "0x0" you can't know if the string was NULL or if the string was
actually "0x0".
--
You are receiving this mail because:
You are the assignee for the bug.