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 16:45:07 +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
--- Comment #2 from David Smith <dsmith at redhat dot com> ---
(In reply to David Smith from comment #1)
> Perhaps we need a kernel_string3() function, which would look like this:
>
> ====
> function kernel_string3:string (addr:long) {
> try { return kernel_string(addr) } catch { return sprintf("%p", addr) }
> }
> ====
>
> This would either return the string or return the failing address.
Strangely enough, the above matches the behavior of kernel_string_quoted, which
also either returns the quoted string or the failing address.
--
You are receiving this mail because:
You are the assignee for the bug.