search for: tracers

Hi, I'm trying to build VMKit from SVN, and I'm getting a bunch of errors that all seem to be related to the TRACER macro not getting defined: llvm[3]: Compiling Assembly.cpp for Release+Asserts build In file included from Assembly.cpp:15: Assembly.h:140: error: variable or field ‘TRACER’ declared void In file included from Assembly.cpp:19: N3.h:109: error: variable or field ‘TRACER’

Hi All, Thanks Nicolas for pointing out that I needed --enable-targets=x86,cpp for my llvm config to get vmkit to build. The process gets a lot farther but fails in different places depending upon the vmkit config (Can you please see the three case below?). My machine is a intel core i7 running ubuntu karmic and gcc 4.4.1. What arch/OS/distro/gcc do you all have VMKit working on? thanks for

Hi On Fri, 27 Feb 2009 22:39:06 +0100 Vegard Nossum <vegard.nossum at gmail.com> wrote: > I actually wanted to ask some questions about Nouveau and the NVIDIA > drivers. I was wondering if there would be any point in extending > kmemcheck to track this driver's use of kernel memory. We could quite > easily make a "memory access tracer", which would show all the

I got packet tracer to install just fine with Wine, but when I launch it...the splash screen comes up and then it just closes. Any advice? This is the first program that I've ever tried to run with Wine.

On the off chance anyone here is interested in more performance results, I compiled and ran the fastest of the implementations of the ray tracer in C++ from my language comparison: http://www.ffconsultancy.com/languages/ray_tracer/ This is a small program with a relatively large hotpath. Specifically, around 30% of the time is spend in the ray sphere intersection but another 30% is also

At the most recent Xen Summit, Thomas Friebel presented a paper ("Preventing Guests from Spinning Around", http://xen.org/files/xensummitboston08/LHP.pdf) investigating the interactions between spinlocks and virtual machines. Specifically, he looked at what happens when a lock-holding VCPU gets involuntarily preempted. The obvious first order effect is that while the VCPU is not

At the most recent Xen Summit, Thomas Friebel presented a paper ("Preventing Guests from Spinning Around", http://xen.org/files/xensummitboston08/LHP.pdf) investigating the interactions between spinlocks and virtual machines. Specifically, he looked at what happens when a lock-holding VCPU gets involuntarily preempted. The obvious first order effect is that while the VCPU is not

At the most recent Xen Summit, Thomas Friebel presented a paper ("Preventing Guests from Spinning Around", http://xen.org/files/xensummitboston08/LHP.pdf) investigating the interactions between spinlocks and virtual machines. Specifically, he looked at what happens when a lock-holding VCPU gets involuntarily preempted. The obvious first order effect is that while the VCPU is not

(Under 2.2.0, Mac) I have been unable to reduce this to a simple case, so I'll include my full code, and my intentions. The problem I'm trying to solve is that while many defaults (eg. na.rm=F, drop=T) make sense for interactive programming, they tend to be a bit of a pain when developing a package. For example, I often forget to use drop=FALSE, only test with multiple columns and then

Hi, I encountered a booting problem with memdisk 2.83, USB and IBM Thinkpad T61, apparently the same issue as described here: http://syslinux.zytor.com/archives/2008-April/009850.html The boot process always stops after "Loading boot sector... booting...". With debug tracers enabled, the last few output lines are: Loading boot sector... FR<p>Dbooting... FR<p>DFR<p>DFR<p>DFR<p>DFR<p>DFR<p><DFR<p>DFR<p>DFR<p>DFR<p>DFR<p>DFR<p>DFR<p>DFR <p>DFR<p>DFR<p>DFR<p>DFR&...

Hello everyone, I just thought I would let people here know that ldc (llvm backend for the D Programming Language) is getting pretty usable (a few larger libraries compile) and it now has x86-64 support added. I decided to run some timings on some D and C++ code to compare ldc to dmd (the mainline compiler), gdc (the gcc based D compiler) and g++. I used a ray tracing program found in this

?ukasz Daniluk reported that on a RHEL kernel that his machine would lock up after enabling function tracer. I asked him to bisect the functions within available_filter_functions, which he did and it came down to three: _paravirt_nop(), _paravirt_ident_32() and _paravirt_ident_64() It was found that this is only an issue when noreplace-paravirt is added to the kernel command line. This means

?ukasz Daniluk reported that on a RHEL kernel that his machine would lock up after enabling function tracer. I asked him to bisect the functions within available_filter_functions, which he did and it came down to three: _paravirt_nop(), _paravirt_ident_32() and _paravirt_ident_64() It was found that this is only an issue when noreplace-paravirt is added to the kernel command line. This means

On Oct 27, 2008, at 11:03 PM, Kelly W wrote: > Hello everyone, > > I just thought I would let people here know that ldc (llvm backend > for the D Programming Language) is getting pretty usable (a few > larger libraries compile) and it now has x86-64 support added. I > decided to run some timings on some D and C++ code to compare ldc to > dmd (the mainline compiler),

Hi. I became study vmkit and did not find any methods to understand its structure and functional capabilities expect building toyVM. In process of its building I have encountered with some problems: 1) I don't understand how and when tracer is called by collector, because methods MandelPix::tracer and Picture::tracer I had wrote are never called by collector; 2) I don't understand how I

Hi, I going through the Interpreter class source code and I think making almost all the visit methods (maybe not visitInstruction yet) would really help anybody that wants to create any sort of tracer or similar. Would be a patch in this case worthy? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL:

...INUX. > 2) William Kensington already saw a similar behavior wherein an ISOLINUX > image failed before parsing the config. > 3) It feels like this is a moving target where gcc keeps changing and > different results get reported. > 4) We'll likely need to make code akin to the old tracers (on screen or > serial) to log progress. > > --Gene > Upstream folks could be of help https://bugzilla.redhat.com/show_bug.cgi?id=1243117

On Thu, 2015-01-29 at 15:56 +0800, Kevin Laurie wrote: > Hey Joseph > Thanks. Strace seems like a very useful tool > Only problem is that I dont think it is maintained on ubuntu. > Tried to run:- > apt-get install strace but could not download it. > Might need to download and build it. Do you know any other way of getting > it? > Thanks > Kevin A. try apt-cache search

I would like to trace functions, displaying their arguments and return value, but I haven't been able to figure out how to do this with the 'trace' function. After some thrashing, I got as far as this: fact <- function(x) if(x<1) 1 else x*fact(x-1) tracefnc <- function() dput(as.list(parent.frame()), # parent.frame() holds arg list

I would like to trace functions, displaying their arguments and return value, but I haven't been able to figure out how to do this with the 'trace' function. After some thrashing, I got as far as this: fact <- function(x) if(x<1) 1 else x*fact(x-1) tracefnc <- function() dput(as.list(parent.frame()), # parent.frame() holds arg list