similar to: where do kernel data types come from?

Hello everybody! How do people generate the Compact Type Format (CTF) section? Do you have a special parser or employ gcc debug information? Is there any open utility to do this job? Best regards, Yaroslav

Hi, ctfconvert is particularly unhappy about that (e.g., ERROR: ctfconvert: die 141: base type without name). Is it intended behavior? Simple testcase: int main(void) { int i[2]; return 0; } dwarfdump output: clang version 3.0 (tags/RELEASE_30/final): [...] LOCAL_SYMBOLS: [...] <3>< 120> DW_TAG_variable DW_AT_name i

kill dead ocfs_empty stuff, cleanup d_revalidate handling. Index: dcache.c =================================================================== --- dcache.c (revision 1091) +++ dcache.c (working copy) @@ -44,24 +44,11 @@ #define OCFS_DEBUG_CONTEXT OCFS_DEBUG_CONTEXT_DCACHE -static int ocfs_empty_func(struct dentry *dentry, void *ignore); - -/* - * ocfs_dentry_revalidate() - * - */ -#if

ocfs2 was hand-calling vfs_follow_link(), but there's no point to that. Let's use page_follow_link_light() and nd_set_link(). Signed-off-by: Joel Becker <joel.becker at oracle.com> --- fs/ocfs2/symlink.c | 77 +++++++++++++++++++++++++--------------------------- 1 files changed, 37 insertions(+), 40 deletions(-) diff --git a/fs/ocfs2/symlink.c b/fs/ocfs2/symlink.c index

Hi Dean, I haven't looked very closely at XRay so far, but I'm wondering if making CTF (common trace format, e.g. see http://diamon.org/ctf/) the default format for XRay traces would be useful? It seems it'd be nice to be able to reuse some of the tools that already exist for CTF, such as a graphical viewer (http://tracecompass.org/) or a converter library

Way back in r107027, we started preserving type information of local variables of functions that are optimized away. This seemed strange to me so I dug into the history: apparently, this is so that ctfconvert can find these types (so they can be exposed in dtrace). E.g., this commit made it so that for this C code: static void foo(void) { struct X { int b; } v; } we always get the type

Hi llvm-dev, Recently, we've committed the beginnings of the llvm-xray [0] tool which allows for conveniently working with both XRay-instrumented libraries as well as XRay trace/log files. In the course of the review for the conversion tool [1] which turns a binary/raw XRay log file into YAML for human consumption purposes, a question arose as to how we intend to allow users to develop tools

On Feb 11, 2012, at 7:51 AM, Yuri Pankov <yuri.pankov at gmail.com> wrote: > Hi, > > ctfconvert is particularly unhappy about that (e.g., ERROR: ctfconvert: > die 141: base type without name). Is it intended behavior? Not that I know of, please file a bug. Thanks! -eric

This is a belated heads up to let you know that I have merged DTrace to the releng7 branch in the nick of time before the feature freeze for 7.1. Those astute mailing list readers will note that the commit message appears to have gone missing. Well, either the dog ate it or subversion decided that it was for certain eyes only (and not yours, or mine). I have added a note to src/UPDATING

OK, I am trying to dtrace isp(4) module in freebsd 7. each obj file is converted using: ctfconvert -L VERSION isp_freebsd.o and using "ctfdump isp_freebsd.o" I can see CTF info embedded in the .o file but in the linked kernel module, I found much less CTF info inside it. I guess I should use "ctfmerge" to combine the CTF info from each obj file into the final kernel module,

Author: dmick Repository: /hg/zfs-crypto/gate Revision: cbab1f3458114bfa0299fad44636dcd38de5f505 Log message: 6241314 ctfconvert should understand SPARC real types in DWARF 6313293 ctfstabs is confused by gcc''s output 6268862 add more gcc support routines to a few places 6272005 gcc and cmd/mdb don''t get along 6273966 gcc and common/dis don''t get along Files: create:

Hi all, I want to open a device(/dev/sda1, /dev/hda2 etc) in which my file exists. I've used 'stat' system call to get the device id. But now I want the device name from this id(st_dev). How to get that one? Or Do you have any other method to know the device name where my file resides? Thanks Bollywood, fun, friendship, sports and more. You name it, we have it on

I want to go a lot deeper with my tracing of MySQL and to do so I want to look into MySQL Thread Descriptors (class THD). Inside is a great bulk of information utilized by a great many of the core functions within MySQL... I really want to get in there. So far I''ve had no luck though. It''s a C++ class, and I''m afraid that I''m approaching it like a C struct,

Hi all, OK, so this at first looked like a clear cut "Don''t do it, or at worst handle the results" issue my customer has come to me with, but the more we discuss it, the more it looks like we should have better ways of dealing with this issue. > We have user defined dtrace probe points in the application which use > as parameter 64 bit values: > > provider adv {

everyone, Just out of curiosity, I did a dtrace -n ''syscall:::entry { @num[execname, probefunc] = count(); }'' and looked at the entries produced by ''rm''. I see everything that rm did, *except* the unlinkat - which is unfortunate because I want to trace which processes have deleted which files. So - does dtrace contain unlinkat as a probe for a system call?

My leaky memory says we moved entry-point into some form of debug record in the standard libraries, circa Solaris 8/9. Before that, my group maintained text files that listed all the entry-points and their parameters for libraries like libc.so, so that we could print out parameter values in apptrace(8). There''s a (small) chance the records are complete enough that dtrace could use the

> On May 6, 2016, at 3:48 PM, Adrian Prantl via llvm-dev <llvm-dev at lists.llvm.org> wrote: > >> >> On May 6, 2016, at 3:40 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: >> >> >>> On May 6, 2016, at 3:17 PM, Adrian Prantl <aprantl at apple.com> wrote: >>> >>> >>>> On May 6, 2016, at 1:17 PM, Peter

I have a sunw2100z (dual AMD) 2GB memory, I refresh installed nvx_35 on scsi disk (on board controller), then I enabled anon tracing fbt::xxx_attach:entry { self->trace = 1; } fbt::: /self->trace/ {} fbt::xxx_attach:return { self->trace = 0; } xxx_attach is HBA driver''s attach entry point. #dtrace -AFs xxx.d # reboot then reboot gives enabling probe 0..... WARNING:

> On May 6, 2016, at 4:01 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > >> On May 6, 2016, at 3:53 PM, Adrian Prantl <aprantl at apple.com> wrote: >> >>> >>> On May 6, 2016, at 3:48 PM, Adrian Prantl via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>>> >>>> On May 6, 2016, at 3:40 PM, Mehdi

Hi, I am trying to trace some functions that are executed at detach time, and it seems that just having dtrace around to instrument the module is causing a short circuit, whereas modunload will return (device busy). I understand that this makes sense, but how can I get around this if I want to trace stuff at detach time? Thanks, --S