search for: trace_call

This version doesn't crash or cause hung processes or stuck mountpoints, so that's an improvement. Rich.

This patch is just for review. It enables FUSE support in the API via two new calls, 'guestfs_mount_local' and 'guestfs_umount_local'. FUSE turns out to be very easy to deadlock (necessitating that the machine be rebooted). Running the test from the third patch is usually an effective way to demonstrate this. However I have not yet managed to produce a simple reproducer that

This changes the proposed API slightly. Previously 'mount-local' generating a 'mounted' event when the filesystem was ready, and from the 'mounted' event you had to effectively do a fork. Now, 'mount-local' just initializes the mountpoint and you have to call 'mount-local-run' to enter the FUSE main loop. Between these calls you can do a fork or whatever

...lot of really unfortunate constraints on compilation -- it requires asm goto, pushsection and popsection, etc. I would much rather provide a much more direct way to represent a patchable nop and the addresses of label within a function. For example, I could imagine something like: ``` if (0) { trace_call: /* code to call the trace function */ } patch: __builtin_patchable_nop() __builtin_save_labels(trace_call, patch) ``` But someone can probably design a much better way to represent this in Clang. The advantages I see here (admittedly, mostly for the implementation in Clang and LLVM): 1) It a...

...om> --- fuse/guestmount.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/fuse/guestmount.c b/fuse/guestmount.c index bd7ba50..a9bf4e3 100644 --- a/fuse/guestmount.c +++ b/fuse/guestmount.c @@ -583,7 +583,7 @@ fg_open (const char *path, struct fuse_file_info *fi) { TRACE_CALL ("%s, 0%o", path, fi->flags); - int flags = fi->flags & 3; + int flags = fi->flags & O_ACCMODE; if (read_only && flags != O_RDONLY) return -EROFS; -- 1.7.9.rc2

Asm goto feature was introduces to GCC in order to optimize the support for tracepoints in Linux kernel (it can be used for other things that do nop patching). GCC documentation describes their motivating example here: https://gcc.gnu.org/onlinedocs/gcc-4.8.4/gcc/Extended-Asm.html #define TRACE1(NUM) \ do { \

...and trace enabled flag", + "\ +Return the command trace flag."); + ] (* daemon_functions are any functions which cause some action @@ -4630,6 +4656,52 @@ check_state (guestfs_h *g, const char *caller) "; + (* Generate code to generate guestfish call traces. *) + let trace_call shortname style = + pr " if (guestfs__get_trace (g)) {\n"; + + let needs_i = + List.exists (function + | StringList _ | DeviceList _ -> true + | _ -> false) (snd style) in + if needs_i then ( + pr " int i;\n"; + pr "\n" + );...

...n compilation -- it > requires asm goto, pushsection and popsection, etc. > > I would much rather provide a much more direct way to represent a > patchable nop and the addresses of label within a function. For > example, I could imagine something like: > > ``` >   if (0) { trace_call: /* code to call the trace function */ } >   patch: __builtin_patchable_nop() >   __builtin_save_labels(trace_call, patch) > ``` > > But someone can probably design a much better way to represent this > in Clang. The advantages I see here (admittedly, mostly for the > implemen...

...e constraints on compilation -- it requires asm goto, pushsection and popsection, etc. > > I would much rather provide a much more direct way to represent a patchable nop and the addresses of label within a function. For example, I could imagine something like: > > ``` > if (0) { trace_call: /* code to call the trace function */ } > patch: __builtin_patchable_nop() > __builtin_save_labels(trace_call, patch) > ``` > > But someone can probably design a much better way to represent this in Clang. The advantages I see here (admittedly, mostly for the implementation in...

...; 4 - even more Verbose than 3 ; ; default value: 0 ; debug=0 ; the big trace ; ; default value: [not set] ; ;tracefile=/var/log/misdn.trace tracefile=/var/log/asterisk/misdn.trace ; single call trace files ; set to true if you want to have them ; they depend on debug level ; ; default values: trace_calls : false ; trace_dir : /var/log/ ; ;trace_calls=false ;trace_dir=/var/log/ ; set to yes if you want mISDN_dsp to bridge the calls in HW ; ; default value: yes ; bridging=no ; stops dialtone after getting first digit on nt Port ; ; default value: yes ; stop_tone_after_first_digit...

Hi, this patch serie adds a new GUID type in the generator, which would do the same as String, but also validating (just in the C output) the passed GUID string. This allows to reject invalid GUIDs before passing them to low-level tools. Pino Toscano (4): utils: add a function to validate a GUID string generator: add a GUID parameter type generator: generate code for parameter validation

This rather complex set of patches allow non-optargs functions to gain optional arguments, while preserving source and binary backwards compatibility. The problem is that we cannot add an optional argument to an existing function. For example, we might want to add flags to the 'lvresize' API which currently has no optional arguments.

I may have found a source of an A-Ticked HFC 4BRI PCI adapter in Australia, and will be testing one next week if all goes well. I don't want to post the details of the reseller online unless invited to do so, so if nobody replies and says they are interested then I won't :) I'll follow up once I've tested it. Let me know if you want the details. James

libguestfs has used double and triple underscores in identifiers. These aren't valid for global names in C++. (http://stackoverflow.com/a/228797) These large but completely mechanical patches change the illegal identifiers to legal ones. Rich.