This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug translator/22278] the nss client code doesn't handle '-I DIR' well


https://sourceware.org/bugzilla/show_bug.cgi?id=22278

--- Comment #3 from David Smith <dsmith at redhat dot com> ---
(In reply to Frank Ch. Eigler from comment #1)
> The http client/server pair should try to handle this case (maybe by zipping
> up that -I path).  Wouldn't worry about the old client/server.

The nss client/server does handle this case, it just doesn't handle it well. It
does copy the tapset directory over, but mangles the command line. If I'm
reading the "client" directory correctly, with --use-server the stap command
line that goes over to the server ends up looking like:

# stap tapset/home/dsmith/tapset -I tapset -v -e 'probe oneshot { foo() }'

which is clearly wrong.

The http client/server shares code/ideas with the nss client/server, and I'm
sure the same problem exists in the http client/server. I was wondering how the
nss client/server handled this when I found the problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]