This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/13878] c++ stl decomposition functions
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Tue, 20 Mar 2012 19:39:38 +0000
- Subject: [Bug tapsets/13878] c++ stl decomposition functions
- Auto-submitted: auto-generated
- References: <bug-13878-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13878
--- Comment #3 from Josh Stone <jistone at redhat dot com> 2012-03-20 19:39:38 UTC ---
(In reply to comment #2)
> > This should work already, thanks to bug 12136. However, note that the default
> > module for a @cast without context is "kernel"
>
> Ah. The error message should include a hint to that effect.
It currently says:
semantic error: type definition 'std::string' not found: [location]
Would it suffice to amend like this? ... not found in "$module": ...
> > Back on the $subject, I wonder whether stl types are fixed enough for us to
> > have general functions? I'm thinking especially between --std versions, might
> > the layout of these objects vary?
>
> That's why nature invented @defined().
> Whether it's enough for everything, I dunno.
I'm not sure how @defined would help. It can let you vary your cpp_string()
implementation depending on the chosen module, but my concern is with knowing
the layout of the user's incoming ptr, for which we have no type info. Bug
13664 could make that pretty snazzy though...
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.