search for: loadobject

Hey all-- I'm brand new to R, and have just installed the ChemoSpec because I'd like to do PCA of NMR datasets. I was following along with the vignette and trying to load the sample data as follows... NMRTest <- loadObject("SrE.NMR.RData") ...and got the following error message: Error: could not find function "loadObject" I tried searching the above error message on the forum, but there were "0 matching posts." I'm hoping someone can tell me what I'm doing wrong! Best, ?Dav...

...swfdec_player.c | 5 libswfdec/swfdec_player_internal.h | 1 libswfdec/swfdec_xml.c | 177 ------------------------------ libswfdec/swfdec_xml_as.c | 17 +- libswfdec/swfdec_xml_as.h | 14 -- test/trace/Makefile.am | 7 + test/trace/loadobject-5.swf |binary test/trace/loadobject-5.swf.trace | 46 +++++++ test/trace/loadobject-6.swf |binary test/trace/loadobject-6.swf.trace | 46 +++++++ test/trace/loadobject-7.swf |binary test/trace/loadobject-7.swf.trace | 46 +++++++ test/trace/loadobject.as |...

...1 libswfdec/swfdec_as_strings.c | 1 libswfdec/swfdec_initialize.as | 45 ++++++++++ libswfdec/swfdec_initialize.h | 163 ++++++++++++++++++++++++-------------- libswfdec/swfdec_load_object.c | 16 ++- libswfdec/swfdec_loadvars_as.c | 70 ++++++++++++++++ test/trace/loadobject-5.swf |binary test/trace/loadobject-5.swf.trace | 19 +++- test/trace/loadobject-6.swf |binary test/trace/loadobject-6.swf.trace | 19 +++- test/trace/loadobject-7.swf |binary test/trace/loadobject-7.swf.trace | 19 +++- test/trace/loadobject.as | 5 + test/tr...

...| 1 test/trace/forin-delete-6.swf |binary test/trace/forin-delete-6.swf.trace | 1 test/trace/forin-delete-7.swf |binary test/trace/forin-delete-7.swf.trace | 1 test/trace/forin-delete.as | 14 + test/trace/loadobject-5.swf |binary test/trace/loadobject-5.swf.trace | 57 ++++++ test/trace/loadobject-6.swf |binary test/trace/loadobject-6.swf.trace | 57 ++++++ test/trace/loadobject-7.swf |binary test/trace/loadobject-7.swf.trace...

...utStream$PeekInputStream.readFully(Unknown Source) at java.io.ObjectInputStream$BlockDataInputStream.readShort(Unknown Source) at java.io.ObjectInputStream.readStreamHeader(Unknown Source) at java.io.ObjectInputStream.<init>(Unknown Source) at net.sf.jasperreports.engine.util.JRLoader.loadObject(JRLoader.java:84) at net.sf.jasperreports.engine.JasperFillManager.fillReport(JasperFillManager.java:342) at XmlJasperInterface.report(XmlJasperInterface.java:74) at XmlJasperInterface.main(XmlJasperInterface.java:58) NESTED BY : net.sf.jasperreports.engine.JRException: Error loading object...

...or one thing, unless you very carefully maintain the association with the original object via back-channels there will be no way of knowing which section belongs to which object file. With a bit of cleanup though, we could do something more like this: const RuntimeDyld::JITObject& JO = RTDyld.loadObject(Object); // ... RTDyld.resolveRelocations(); DEBUG( for (const RuntimeDyld::JITObject::Section& S : JO.sections()) if (S.isText()) Disassemble(S.getAddr(), S.getSize()); ); How does that look? Cheers, Lang. On Wed, Sep 17, 2014 at 3:08 PM, Philip Reames <listmail at philipre...

...ase by sorting the traced arrays. Forgot to add propflags test to Makefile.am Add test for deleting properties when in for in loop Implement hitTest for x, y coordinates (without shapeFlag) Forgot to add forin-delete test to Makefile.am (sigh) Move XML.load code to new LoadObject class, make it work with any Object Set _bytesLoaded and _bytesTotal properties in LoadObject Set _bytesLoaded to 0 when LoadObject is started Reformat LoadObject code a little Fix load method crash when called without params and fix it's return values Allow callin...

While using MCJIT, when I define a function with name Fn_.._lib_rc-variant.lp0_17_0x706970 ExecutionEngine::getPointerToFunction fails to locate it (returns 0). There is no problem if the function is named Fn_0x706970. There is no problem with those names using the traditional JIT. Is there any special limitation on function names for MC/MCJIT?

...kka.lampila at iki.fi> Date: Sat Sep 1 22:08:11 2007 +0300 LoadVars test was missing from Makefile.am diff --git a/test/trace/Makefile.am b/test/trace/Makefile.am index 22b7a95..484da67 100644 --- a/test/trace/Makefile.am +++ b/test/trace/Makefile.am @@ -575,6 +575,14 @@ EXTRA_DIST = \ loadobject-6.swf.trace \ loadobject-7.swf \ loadobject-7.swf.trace \ + loadvars.as \ + loadvars-5.swf \ + loadvars-5.swf.trace \ + loadvars-6.swf \ + loadvars-6.swf.trace \ + loadvars-7.swf \ + loadvars-7.swf.trace \ + loadvars.txt \ local.swf \ local.swf.trace \ lots-of-arguments.as \ diff-tree cc6...

...| 2 libswfdec/swfdec_load_object.c | 81 libswfdec/swfdec_sprite_movie_as.c | 19 libswfdec/swfdec_system_security.c | 1 test/trace/Makefile.am | 72 test/trace/loadobject-bom-5.swf |binary test/trace/loadobject-bom-5.swf.trace | 27 test/trace/loadobject-bom-6.swf |binary test/trace/loadobject-bom-6.swf.trace | 31 test/trace/loadobject-bom-7.swf |bina...

...Manager::startFunctionBody () (gdb) where #0 0x000000010000349e in llvm::MCJITMemoryManager::startFunctionBody () #1 0x0000000100003ea0 in llvm::RuntimeDyldImpl::extractFunction () #2 0x00000001000059a5 in llvm::RuntimeDyldMachO::loadSegment64 () #3 0x000000010000493d in llvm::RuntimeDyldMachO::loadObject () #4 0x0000000100003cf9 in llvm::RuntimeDyld::loadObject () #5 0x00000001000032e5 in llvm::MCJIT::MCJIT () #6 0x00000001000021c2 in llvm::MCJIT::createJIT () #7 0x0000000100023274 in llvm::EngineBuilder::create () #8 0x0000000100001417 in lRunTest (fn=0x7fff5fbffb3a "a.bc") at bug.c...

...._lib_rc_2D_variant.lp0_17_0x706970 > When you call getPointerToFunction in MCJIT, it will ultimately call > RuntimeDyldImpl::getSymbolLoadAddress to look the name up in a table > of known function names. That table gets built from the emitted object > image during the RuntimeDyldImpl::loadObject call. If you set a > breakpoint in that function you can see all the symbol names that get > processed and it will probably tell you why the function isn't being > found. RuntimeDyldImpl::loadObject loads the mangled names, but RuntimeDyldImpl::getSymbolLoadAddress does not try to &qu...

...------------------------------------------------------------------------------------------------ If you want to create both csv file and an object directly from the file path; > library(R.utils) > saveObject(WV6_Data_R, "~/docdis/input/ch2/WV6_Data_R_v_2016_01_01.csv") > d <- loadObject("~/docdis/input/ch2/WV6_Data_R_v_2016_01_01.csv") --------------------------------------------------------------------------------------------------- I am so sorry for my mistake. For your reference, I put the whole contents of my last e-mail message below. ------------------the followi...

...--------------------------------------------------------- -------------------------------------- If you want to create both csv file and an object directly from the file path; > library(R.utils) > saveObject(WV6_Data_R, "~/docdis/input/ch2/WV6_Data_R_v_2016_01_01.csv") > d <- loadObject("~/docdis/input/ch2/WV6_Data_R_v_2016_01_01.csv") ------------------------------------------------------------ --------------------------------------- I am so sorry for my mistake. For your reference, I put the whole contents of my last e-mail message below. ------------------the follow...

...ance which is held by RuntimeDyldELF. For those who are visually oriented, I am attaching a diagram which shows the object relationships. I would like to change this by introducing an ObjectBuffer which would be allocated by the MCJIT object at compilation time and then passed to the RuntimeDyld::loadObject. RuntimeDyld::loadObject would hand this ObjectBuffer off to the new ObjectImage instance (which it already creates today). The ObjectImage would be returned from the RuntimeDyld::loadObject to MCJIT and MCJIT would own that object. Again, a diagram is attached. ------------------- Object cach...

...ance which is held by RuntimeDyldELF. For those who are visually oriented, I am attaching a diagram which shows the object relationships. I would like to change this by introducing an ObjectBuffer which would be allocated by the MCJIT object at compilation time and then passed to the RuntimeDyld::loadObject. RuntimeDyld::loadObject would hand this ObjectBuffer off to the new ObjectImage instance (which it already creates today). The ObjectImage would be returned from the RuntimeDyld::loadObject to MCJIT and MCJIT would own that object. Again, a diagram is attached. ------------------- Object cach...

...9E68EEE88 0x00000079E68EEC98 0x00000079E68EEC78), llvm::object::SectionRef::getContents() + 0x55 bytes(s), c:\llvm\llvm\include\llvm\object\objectfile.h , line 375 + 0x2D byte(s) 0x00007FF65EA1E516 (0x00000079E6A5DEA0 0x00000079E68EEFF0 0x00000079E6A4AC40 0xCCCCCCCCCCCCCCCC), llvm::RuntimeDyldImpl::loadObjectImpl() + 0x4D6 bytes(s), c:\llvm\llvm\lib\executionengine\runtimedyld \runtimedyld.cpp, line 186 + 0x25 byte(s) 0x00007FF65EA431AC (0x00000079E6A5DEA0 0x00000079E68EF708 0x00000079E6A4AC40 0x00000079E68EF0C8), llvm::RuntimeDyldCOFF::loadObject() + 0x3C bytes(s), c:\llvm\llvm\lib\executionengine\runt...

...iple separate outputs which one would like to compare? (I have read something about environments, but I understood it's only for functions. I could create environments, but was not succesful in using them at all (location change or separate sandbox). Functions saveCache, loadCache, saveObject, loadObject is not really what I have in mind, too -- saveObject(list=ls(), "NewObjectFile") is not a solution either...) Thanks for any hint in advance. Cheers, Zroutik [[alternative HTML version deleted]]

If save() fails because an object is not found, it should not overwrite an existing file. > a <- 1:9 > save(a, file = "a.rda") > rm(a) > load("a.rda") > a [1] 1 2 3 4 5 6 7 8 9 > rm(a) > save(a, file = "a.rda") Error in save(a, file = "a.rda") : object 'a' not found > load("a.rda") Error in

...RuntimeDyldELF. > > For those who are visually oriented, I am attaching a diagram which shows the object relationships. > > I would like to change this by introducing an ObjectBuffer which would be allocated by the MCJIT object at compilation time and then passed to the RuntimeDyld::loadObject. RuntimeDyld::loadObject would hand this ObjectBuffer off to the new ObjectImage instance (which it already creates today). The ObjectImage would be returned from the RuntimeDyld::loadObject to MCJIT and MCJIT would own that object. > > Again, a diagram is attached. > > > ---...