search for: symbol_name

Hello Everyone , We have the legacy code ,that uses the .stabs directive quiet often in the source code like .stabs "symbol_name", 100, 0, 0, 0 + .label_one f; .label_one stmt and ,the above code is wrapped with the inline asm in the c source file . we are using clang 3.8(with lto) and as you know that builtin assembler / MC streamer don't have support fir .stabs directive. we are looking to emul...

...eginning + * of a function. + */ +static void __init populate_kprobe_blacklist(struct kprobe_blackpoint **start, + struct kprobe_blackpoint **end) { - int i, err = 0; + struct kprobe_blackpoint **iter, *bp; unsigned long offset = 0, size = 0; char *modname, namebuf[128]; const char *symbol_name; - void *addr; - struct kprobe_blackpoint *kb; + + for (iter = start; (unsigned long)iter < (unsigned long)end; iter++) { + bp = *iter; + symbol_name = kallsyms_lookup(bp->start_addr, + &size, &offset, &modname, namebuf); + if (!symbol_name) + continue; + + bp->range =...

Hi, We have a lot of non-trivial logic accumulated in the implementation of llvm-symbolizer tool (tools/llvm-symbolizer/LLVMSymbolize.{h,cpp}), for instance: * dynamic dispatch between DWARF and PDB debug info; * building address->symbol_name mapping from object file (with special cases for PowerPC function descriptor section, and COFF export tables); * finding debug info stored in separate files (.dSYM files on Darwin, ELF .gnu_debuglink section, etc.); * demangling (with platform-specific implementations for Windows and Unix). I prop...

...need to do for a Foo target: Implement 3 classes: * FooTargetStreamer : public MCTargetStreamer * FooTargetAsmSreamer : public FooTargetStreamer * FooTargetELFStreamer : public FooTargetStreamer FooTargetStreamer should have a pure virtual method for each directive. For example, for a ".bar symbol_name" directive, it should have virtual emitBar(const MCSymbol &Symbol) = 0; The FooTargetAsmSreamer and FooTargetELFStreamer classes implement the method. The assembly streamer just prints ".bar symbol_name". The object streamer does whatever is needed to implement .bar in the objec...

...37526 For the context, there is a comment in compiler-rt/lib/fuzzer/FuzzerExtFunctionsWeak.cpp: // Implementation for Linux. This relies on the linker's support for weak // symbols. We don't use this approach on Apple platforms because it requires // clients of LibFuzzer to pass ``-U _<symbol_name>`` to the linker to allow // weak symbols to be undefined. That is a complication we don't want to expose // to clients right now. That makes sense, but with current implementation, you cannot use libFuzzer's interface functions other than LLVMFuzzerTestOneInput. Below is a small exampl...

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. At this moment, I

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. At this moment, I

...> > > > We have a lot of non-trivial logic accumulated in the > > implementation of llvm-symbolizer tool > > (tools/llvm-symbolizer/LLVMSymbolize.{h,cpp}), for instance: > > > > * dynamic dispatch between DWARF and PDB debug info; > > * building address->symbol_name mapping from object file (with special > cases > > for PowerPC function descriptor section, and COFF export tables); > > * finding debug info stored in separate files (.dSYM files on Darwin, ELF > > .gnu_debuglink section, etc.); > > * demangling (with platform-specific i...

...-trivial logic accumulated in the >>> > implementation of llvm-symbolizer tool >>> > (tools/llvm-symbolizer/LLVMSymbolize.{h,cpp}), for instance: >>> > >>> > * dynamic dispatch between DWARF and PDB debug info; >>> > * building address->symbol_name mapping from object file (with special >>> cases >>> > for PowerPC function descriptor section, and COFF export tables); >>> > * finding debug info stored in separate files (.dSYM files on Darwin, >>> ELF >>> > .gnu_debuglink section, etc.); &gt...

...t;>>> > implementation of llvm-symbolizer tool >>>>> > (tools/llvm-symbolizer/LLVMSymbolize.{h,cpp}), for instance: >>>>> > >>>>> > * dynamic dispatch between DWARF and PDB debug info; >>>>> > * building address->symbol_name mapping from object file (with >>>>> special cases >>>>> > for PowerPC function descriptor section, and COFF export tables); >>>>> > * finding debug info stored in separate files (.dSYM files on >>>>> Darwin, ELF >>>>>...

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. This series

Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've tried to implement new NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined, it is easy to maintain. This series

Hi, Here is the version 3 of NOKPORBE_SYMBOL series. Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've introduced NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined

Hi, Here is the version 3 of NOKPORBE_SYMBOL series. Currently the blacklist is maintained by hand in kprobes.c which is separated from the function definition and is hard to catch up the kernel update. To solve this issue, I've introduced NOKPROBE_SYMBOL() macro for making kprobe blacklist at build time. Since the NOKPROBE_SYMBOL() macros can be placed right after the function is defined

What is the state of GPLPV and Windows 8? I am currently running tests with Windows 8 and GPLPV rev956 and operations (disk IO, net IO) look good. There seems to be a problem with shutdown/reboot where Windows hangs somewhat and displays a warning about improper shutdown on next reboot. Regards Andreas

Thanks, the whole iSCSI LUN have been passed to the VM. But I test it with scsicmd, and found that the driver may be not support SPC-3, but if i use this by microsoft iscsi initiator, I can pass all the scsi3_test tests. Tool can be found here: http://www.symantec.com/business/support/index?page=content&id=TECH72086 It's this means that the scsi passthrough windows driver does not

...rn Error(L, "unexpected token in directive"); - Parser.Lex(); + Lex(); // TODO: set thumb mode // TODO: tell the MC streamer the mode - // getParser().getStreamer().Emit???(); + // getStreamer().Emit???(); return false; } /// ParseDirectiveThumbFunc /// ::= .thumbfunc symbol_name bool ARMAsmParser::ParseDirectiveThumbFunc(SMLoc L) { - const AsmToken &Tok = Parser.getTok(); + const AsmToken &Tok = getTok(); if (Tok.isNot(AsmToken::Identifier) && Tok.isNot(AsmToken::String)) return Error(L, "unexpected token in .syntax directive"); - Stri...

...ed declaration is here heimdal/lib/asn1/gen_template.c: In function ?bitstring_symbol?: heimdal/lib/asn1/gen_template.c:145: warning: declaration of ?basename? shadows a global declaration /usr/include/string.h:604: warning: shadowed declaration is here heimdal/lib/asn1/gen_template.c: In function ?symbol_name?: heimdal/lib/asn1/gen_template.c:209: warning: declaration of ?basename? shadows a global declaration /usr/include/string.h:604: warning: shadowed declaration is here heimdal/lib/asn1/gen_template.c: In function ?template_members?: heimdal/lib/asn1/gen_template.c:484: warning: assignment discards...