search for: symbolsize

...ree. Currently, it is drawing a pedigree with too little space, so the text is overlapping. I'd like to increase the distance between individuals. According to the documentation, I would expect the following to be relevant: http://rss.acs.unt.edu/Rdoc/library/kinship/html/plot.pedigree.html symbolsize controls symbolsize. Default=1. width default=8. For a packed pedigree, the minimum width allowed in the realignment of pedigrees. density defines density used in the symbols. Takes up to 4 different values. mar no comment(s) my pedigree command is similar to: plot(ptemp, width=5, symbolsize=...

...; + idx = lhread_u8(vcpu, (u64)tptr); + } + } + + *result = '\0'; + + /* return to offset to the next symbol */ + return off; +} + +static unsigned long get_symbol_pos(struct lguest_vcpu *vcpu, + struct guest_ksym_stuff *kstuff, + unsigned long addr, + unsigned long *symbolsize, + unsigned long *offset) +{ + unsigned long symbol_start = 0, symbol_end = 0; + unsigned long i, low, high, mid; + + /* do a binary search on the sorted kallsyms_addresses array */ + low = 0; + high = kstuff->num_syms; + + while (high - low > 1) { + mid = (low + high) / 2; + if (kst...

...; + idx = lhread_u8(vcpu, (u64)tptr); + } + } + + *result = '\0'; + + /* return to offset to the next symbol */ + return off; +} + +static unsigned long get_symbol_pos(struct lguest_vcpu *vcpu, + struct guest_ksym_stuff *kstuff, + unsigned long addr, + unsigned long *symbolsize, + unsigned long *offset) +{ + unsigned long symbol_start = 0, symbol_end = 0; + unsigned long i, low, high, mid; + + /* do a binary search on the sorted kallsyms_addresses array */ + low = 0; + high = kstuff->num_syms; + + while (high - low > 1) { + mid = (low + high) / 2; + if (kst...

...+ idx = lgread_u8(lg, (unsigned long)tptr); + } + } + + *result = '\0'; + + /* return to offset to the next symbol */ + return off; +} + +static unsigned long get_symbol_pos(struct lguest *lg, + struct guest_ksym_stuff *kstuff, + unsigned long addr, + unsigned long *symbolsize, + unsigned long *offset) +{ + unsigned long symbol_start = 0, symbol_end = 0; + unsigned long i, low, high, mid; + + /* do a binary search on the sorted kallsyms_addresses array */ + low = 0; + high = kstuff->num_syms; + + while (high - low > 1) { + mid = (low + high) / 2; + if (kst...

...+ idx = lgread_u8(lg, (unsigned long)tptr); + } + } + + *result = '\0'; + + /* return to offset to the next symbol */ + return off; +} + +static unsigned long get_symbol_pos(struct lguest *lg, + struct guest_ksym_stuff *kstuff, + unsigned long addr, + unsigned long *symbolsize, + unsigned long *offset) +{ + unsigned long symbol_start = 0, symbol_end = 0; + unsigned long i, low, high, mid; + + /* do a binary search on the sorted kallsyms_addresses array */ + low = 0; + high = kstuff->num_syms; + + while (high - low > 1) { + mid = (low + high) / 2; + if (kst...

...s(i) > symbols_address(low)) { + symbol_end = symbols_address(i); break; } } @@ -132,8 +138,8 @@ const char *symbols_lookup(unsigned long symbol_end = is_kernel_inittext(addr) ? (unsigned long)_einittext : (unsigned long)_etext; - *symbolsize = symbol_end - symbols_addresses[low]; - *offset = addr - symbols_addresses[low]; + *symbolsize = symbol_end - symbols_address(low); + *offset = addr - symbols_address(low); return namebuf; } --- 2009-07-10.orig/xen/common/symbols-dummy.c 2009-07-13 13:56:07.000000000 +0200 +++ 200...

...1, and then there is a comment in >>>>> getSymbolAuxData which says: >>>>> >>>>> // AUX data comes immediately after the symbol in COFF >>>>> Aux = reinterpret_cast<const uint8_t *>(Symbol.getRawPtr()) + >>>>> SymbolSize; >>>>> >>>>> So I think you just need to write the bytes immediately after the >>>>> coff::symbol. The thing you need to write looks like a >>>>> coff::coff_aux_section_definition structure. >>>>> >>>>> For t...

...s >>>>>> a comment in getSymbolAuxData which says: >>>>>> >>>>>> // AUX data comes immediately after the symbol in COFF >>>>>> Aux = reinterpret_cast<const uint8_t *>(Symbol.getRawPtr()) + >>>>>> SymbolSize; >>>>>> >>>>>> So I think you just need to write the bytes immediately after the >>>>>> coff::symbol. The thing you need to write looks like a >>>>>> coff::coff_aux_section_definition structure. >>>>>> >&g...

...>>> comment in getSymbolAuxData which says: >>>>>>> >>>>>>> // AUX data comes immediately after the symbol in COFF >>>>>>> Aux = reinterpret_cast<const uint8_t *>(Symbol.getRawPtr()) + >>>>>>> SymbolSize; >>>>>>> >>>>>>> So I think you just need to write the bytes immediately after the >>>>>>> coff::symbol. The thing you need to write looks like a >>>>>>> coff::coff_aux_section_definition structure. >>>&gt...

...ment in getSymbolAuxData which says: >>>>>>>> >>>>>>>> // AUX data comes immediately after the symbol in COFF >>>>>>>> Aux = reinterpret_cast<const uint8_t *>(Symbol.getRawPtr()) + >>>>>>>> SymbolSize; >>>>>>>> >>>>>>>> So I think you just need to write the bytes immediately after the >>>>>>>> coff::symbol. The thing you need to write looks like a >>>>>>>> coff::coff_aux_section_definition structure....

...es/LLVMObject.dir/MachOUniversal.cpp.o CMakeFiles/LLVMObject.dir/ModuleSummaryIndexObjectFile.cpp.o CMakeFiles/LLVMObject.dir/Object.cpp.o CMakeFiles/LLVMObject.dir/ObjectFile.cpp.o CMakeFiles/LLVMObject.dir/RecordStreamer.cpp.o CMakeFiles/LLVMObject.dir/SymbolicFile.cpp.o CMakeFiles/LLVMObject.dir/SymbolSize.cpp.o -lxar ../libLLVMBitReader.dylib ../libLLVMCore.dylib ../libLLVMMC.dylib ../libLLVMMCParser.dylib ../libLLVMSupport.dylib -Wl,-rpath, at executable_path/../lib and thus the linkage for llvm-objdump is directly linked against libxar as in the default static lib build. Only the -DLLVM_LINK_LLV...

...umberOfAuxSymbols to 1, and then there is a >>>> comment in getSymbolAuxData which says: >>>> >>>> // AUX data comes immediately after the symbol in COFF >>>> Aux = reinterpret_cast<const uint8_t *>(Symbol.getRawPtr()) + >>>> SymbolSize; >>>> >>>> So I think you just need to write the bytes immediately after the >>>> coff::symbol. The thing you need to write looks like a >>>> coff::coff_aux_section_definition structure. >>>> >>>> For the CheckSum, look at Win...

...al.cpp.o > CMakeFiles/LLVMObject.dir/ModuleSummaryIndexObjectFile.cpp.o > CMakeFiles/LLVMObject.dir/Object.cpp.o > CMakeFiles/LLVMObject.dir/ObjectFile.cpp.o > CMakeFiles/LLVMObject.dir/RecordStreamer.cpp.o > CMakeFiles/LLVMObject.dir/SymbolicFile.cpp.o > CMakeFiles/LLVMObject.dir/SymbolSize.cpp.o -lxar > ../libLLVMBitReader.dylib ../libLLVMCore.dylib ../libLLVMMC.dylib > ../libLLVMMCParser.dylib ../libLLVMSupport.dylib > -Wl,-rpath, at executable_path/../lib > > and thus the linkage for llvm-objdump is directly linked against > libxar as in the default static lib bu...

On Tue, May 24, 2016 at 2:28 PM, Chris Bieneman <beanz at apple.com> wrote: > Jack, > > What version of CMake are you using? > > -Chris Chris, I am using cmake 3.5.2. My read of this problem is as follows. While libLLVM.dylib is being linked against -lxar when -DLLVM_LINK_LLVM_DYLIB:BOOL=ON is passed to cmake, the libLLVM.dylib is created with -Wl,-dead_strip such that

...set coff::symbol::NumberOfAuxSymbols to 1, and then there is a comment in >>> getSymbolAuxData which says: >>> >>> // AUX data comes immediately after the symbol in COFF >>> Aux = reinterpret_cast<const uint8_t *>(Symbol.getRawPtr()) + >>> SymbolSize; >>> >>> So I think you just need to write the bytes immediately after the >>> coff::symbol. The thing you need to write looks like a >>> coff::coff_aux_section_definition structure. >>> >>> For the CheckSum, look at WinCOFFObjectWriter::writeS...

...<fcntl.h> // open() > + > +#include "llvm/ExecutionEngine/JITEventListener.h" > + > +#include "llvm/ADT/Twine.h" > +#include "llvm/DebugInfo/DWARF/DWARFContext.h" > +#include "llvm/Object/ObjectFile.h" > +#include "llvm/Object/SymbolSize.h" > +#include "llvm/Support/Debug.h" > +#include "llvm/Support/Errno.h" > +#include "llvm/Support/FileSystem.h" > +#include "llvm/Support/Mutex.h" > +#include "llvm/Support/MutexGuard.h" > +#include "llvm/Support/raw_ost...

Having something like this available in tree would definitely be useful. For simplicity, why don't we start with support for the second style? This is the long term useful one and would be a good starting point for getting the code in tree. Can you give a pointer to the patch so that I can assess the rough complexity? If it's simple enough, I'd be happy to help get it reviewed

...olds the clue to what you need to do. It looks like you need to set coff::symbol::NumberOfAuxSymbols to 1, and then there is a comment in getSymbolAuxData which says: // AUX data comes immediately after the symbol in COFF Aux = reinterpret_cast<const uint8_t *>(Symbol.getRawPtr()) + SymbolSize; So I think you just need to write the bytes immediately after the coff::symbol. The thing you need to write looks like a coff::coff_aux_section_definition structure. For the CheckSum, look at WinCOFFObjectWriter::writeSection. It looks like its a CRC32 of the actual section contents, which you...

...d to do. It looks like you need to > set coff::symbol::NumberOfAuxSymbols to 1, and then there is a comment in > getSymbolAuxData which says: > > // AUX data comes immediately after the symbol in COFF > Aux = reinterpret_cast<const uint8_t *>(Symbol.getRawPtr()) + > SymbolSize; > > So I think you just need to write the bytes immediately after the > coff::symbol. The thing you need to write looks like a > coff::coff_aux_section_definition structure. > > For the CheckSum, look at WinCOFFObjectWriter::writeSection. It looks > like its a CRC32 of the a...

Hi, On 2016-12-29 13:17:50 -0800, Philip Reames wrote: > Having something like this available in tree would definitely be > useful. Cool. > For simplicity, why don't we start with support for the second style? This > is the long term useful one and would be a good starting point for getting > the code in tree. Works for me. > Can you give a pointer to the patch so that