search for: unloading

...} Writing R Extensions on the other hand doesn't even mention this (AFAIK). I can see how it would be polite to unload the dlls, but doing so seems to cause some weird problems for me with packages that are loaded/unloaded/reloaded. Additionally, there are some mentions that suggest maybe unloading isn't required. From ?library.dynam: > Note that whether or not it is possible to unload a DLL and then reload a revised version of the same file is OS-dependent: see the ?Value? section of the help for dyn.unload. though this shouldn't affect objects that are not modified. Then there...

I have a package that I'm developing that I need to unload the library. Long story short I figured out that the leaving the compiled code loaded lead to a segmentation fault, but unloading the code will fix it. I've read the documentation and it appears that there are several ways to do this? What is the popper accepted current standard for unloading compiled code? The options as I understand them are: 1. dyn.unload 2. library.dynam.unload used with either A. .Last.lib B. .onU...

configure.ac | 1 dev/null |binary test/Makefile.am | 2 test/custom/.gitignore | 2 test/custom/Makefile.am | 85 +++ test/custom/button-events-button-5.swf |binary

Hello, I have a package with a namespace. Because I use Roxygen that overwrites the NAMESPACE file each time it is run, I use a R/zzz.R file with an .onLoad() and .onUnload() functions to take care of loading and unloading my shared library. The problem: if I load my library from a local directory, then the unloading of the package fails, e.g: # loads fine >library(Foo, lib.loc=".Rcheck") >unloadNamespace("Foo") Warning message: .onUnload failed in unloadNamespace() for 'Foo', det...

...he problem is that R segfaults when I unload the library. I initially suspected that the HDF5 function might be corrupting the stack/heap, however, if it is, it's not obvious to me. Upon the successful return from the function, R responds well, and a gc() call works without event (only when unloading do I see the problem). In addition, given that the function returns a single (double) value, I passed a much larger array in order to see whether the HDF routine might be writing off the end of the buffer; the pre-initialized buffer looked OK upon return. Interestingly, when I comment out the cal...

...;t load") checkForTcltk() example(mclapply) } ## test that: checkForTcltk() MCLApply() library(tcltk) checkForTcltk() ## Why can't tcltk just be unloaded? I don't understand, but it is a deep ## problem. ## Consider the ominous warnings in R detach's help: ## ## "Unloading some namespaces has undesirable side effects: e.g. ## unloading ?grid? closes all graphics devices, and on most systems ## ?tcltk? cannot be reloaded once it has been unloaded and may crash ## R if this is attempted." (Note: section of ?detach). ## ## To be fair, that does not say unloading...

Hello, Not sure if this is the right forum: I''m encountering difficulties with o2ib which prevents an LNET shutdown from proceeding: Unloading OpenIB kernel modules:NET: Unregistered protocal family 27 Failed to unload rdma_cm Failed to unload rdma_cm Failed to unload ib_cm Failed to unload ib_sa LustreError: 131-3: Received notification of device removal Please shutdown LNET to allow this to proceed This happens on server and clie...

Second iteration of my endeavour to rid nouveau, radeon and amdgpu of runtime pm ref leaks. Patches 1 to 8 are identical to v1. Patch 9 of v1 modified the DRM core to turn off all CRTCs on driver unload. Based on feedback by Daniel Vetter, I've replaced this with a helper to turn off all CRTCs, which is called by nouveau, radeon and amdgpu on unload. In other words, this is now opt-in. So

On 11/21/2017 03:21 PM, Richard W.M. Jones wrote: > This works OK on x86_64, but fails on our fast new Amberwing (aarch64) > machine. I've attached the test-suite.log file, but I'm not very sure > what's going wrong from that. > I'll see what I can spot... > FAIL: test-parallel-file.sh > =========================== > > read 1/1 bytes at offset 0 > 1

...'t unload their DLLs when they being unloaded themselves. I am surprised by this. Why does R not do this automatically? What is the case for keeping the DLL loaded after the package has been unloaded? What happens if you reload another version of the same package from a different library after unloading?

Thanks, Tomas, Luke, for the clarifications. Then, I have another question. But first, let me introduce how I ended up here, because obviously I just don't go around dyn.unloading things that I've just compiled. I was testing a package with valgrind. Everything ok, no leaks. Great. But I'm always suspicious (probably unjustifiably) of all the memory that is reported as "still reachable", so I wanted to check whether there was any difference if I detach(unlo...

This works OK on x86_64, but fails on our fast new Amberwing (aarch64) machine. I've attached the test-suite.log file, but I'm not very sure what's going wrong from that. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to

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

...then-start new R session. My workflow does not include Rolf's "brazillion" repeats, so the overhead of this approach has not been too painful. The documentation for dyn.unload (via ?dyn.unload) includes the following statement: "The function dyn.unload unlinks the DLL. Note that unloading a DLL and then re-loading a DLL of the same name may or may not work: on Solaris it uses the first version loaded." Eric On Thu, Mar 1, 2018 at 2:21 PM, Rui Barradas <ruipbarradas at sapo.pt> wrote: > Hello, > > In such cases, with C code, I call dyn.unload before loading t...

Hi, In what Asterisk file can I edit for me to temporarily unload such modules. But later I woudl still be able to load them. Thanks Angel ____________________________________________________________________________________ Yahoo! Music Unlimited Access over 1 million songs. http://music.yahoo.com/unlimited -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi folks, I've already searched the mailing list but no one else seems to have my same problem. I'm using Asterisk with the following configuration: Fedora Core 4 (but I also tried Fedora 3) 1 Digium TE110P 1 TDM40B 1 HFC-S 'Cologne' bristuff 0.2.0-RC8o (zaptel 1.0.9.2) I compiled right, I can load kernel modules but when I try to unload wcte11xp module (the one

Otherwise 'modprobe -r' on a module having a dependency on bridge will implicitly unload bridge, bringing down all connectivity that was using bridges. Signed-off-by: Jan Beulich <jbeulich@novell.com> net/bridge/br_if.c | 9 +++++++++ 1 file changed, 9 insertions(+) --- linux-2.6.23-rc8/net/bridge/br_if.c 2007-09-26 09:23:54.000000000 +0200 +++

If one wants to unload compiled code for a package containing a namespace, my understanding is that .onUnload() should be used, with a call to library.dynam.unload(). This is used in e.g., the stats and methods packages, but it appears to me that the compiled code is not being unloaded when the package is detached(). Am I misunderstanding something? Best, Jim > search() [1]

If have a couple patches I found while looking at a panic I was seeing while unloading the nouveau module. Unloading the nouveau module on my optimus notebook machine causes the system to panic. This started occuring when moving from 4.4 to 4.14. These patches make it such that the system does not panic when unloading the module. 4.14 also requires commit 34112bf4935d ("drm/n...

...oaded themselves. >> >> I am surprised by this. Why does R not do this automatically? What is >> the case for keeping the DLL loaded after the package has been >> unloaded? What happens if you reload another version of the same >> package from a different library after unloading? >> >> ______________________________________________ >> R-devel at r-project.org mailing list >> https://stat.ethz.ch/mailman/listinfo/r-devel