search for: cxa_demangl

...targets running on OSS-Fuzz, a continuous > > automated fuzzing service: > > https://github.com/google/oss-fuzz > > https://www.usenix.org/sites/default/files/conference/protected-files/ > usenixsecurity17_slides_serebryany.pdf > > > > It has reported a few bugs in cxa_demangler, clang, and dwarfdump > already, > > and we expect to add more fuzz targets to it soon (llvm-isel-fuzzer, > > clang-format-fuzzer, ...) > > > > A question to everyone: how do we report these bugs properly? > > OSS-Fuzz files bugs automatically into a separate bug...

...some possible feature differences. Looks pretty good, I'm guessing this is because all the string operations aren't getting inlined into the parser anymore. Before this patch: __TEXT __DATA __OBJC others dec hex 247293 0 0 1248 248541 3cadd libc++abi.a(cxa_demangle.cpp.o) After this patch: __TEXT __DATA __OBJC others dec hex 137723 4216 0 6016 147955 241f3 libc++abi.a(cxa_demangle.cpp.o) > > Joerg > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org &g...

...; automated fuzzing service: > >> > https://github.com/google/oss-fuzz > >> > https://www.usenix.org/sites/default/files/conference/ > protected-files/ > >> usenixsecurity17_slides_serebryany.pdf > >> > > >> > It has reported a few bugs in cxa_demangler, clang, and dwarfdump > >> already, > >> > and we expect to add more fuzz targets to it soon (llvm-isel-fuzzer, > >> > clang-format-fuzzer, ...) > >> > > >> > A question to everyone: how do we report these bugs properly? > >> >...

Hi, We have several llvm fuzz targets running on OSS-Fuzz, a continuous automated fuzzing service: https://github.com/google/oss-fuzz https://www.usenix.org/sites/default/files/conference/protected-files/usenixsecurity17_slides_serebryany.pdf It has reported a few bugs in cxa_demangler, clang, and dwarfdump already, and we expect to add more fuzz targets to it soon (llvm-isel-fuzzer, clang-format-fuzzer, ...) A question to everyone: how do we report these bugs properly? OSS-Fuzz files bugs automatically into a separate bug tracker, it can not file bugs to bugzilla. By default,...

...m-dev < llvm-dev at lists.llvm.org> wrote: > > Seems like a reasonable project! Maybe we can get a SoC student to make a > standalone C++ demangler library with a tree API (an unstable one should be > fine), and debuggers can just use that instead of relying on the OS's > cxa_demangle. (I'm really not sure why development tools rely on the > system demangler anyway; surely it's always easier to tell users that > they'd get a better experience with a new debugger than to tell them that > they need to replace their system's C++ standard library?) > &g...

...ort of API to get at the demangler tree? > > Not that i know of :( Seems like a reasonable project! Maybe we can get a SoC student to make a standalone C++ demangler library with a tree API (an unstable one should be fine), and debuggers can just use that instead of relying on the OS's cxa_demangle. (I'm really not sure why development tools rely on the system demangler anyway; surely it's always easier to tell users that they'd get a better experience with a new debugger than to tell them that they need to replace their system's C++ standard library?) > We did this in...

On Sun, Mar 4, 2018 at 12:33 AM, John McCall <rjmccall at apple.com> wrote: > On Mar 3, 2018, at 11:30 PM, Daniel Berlin via cfe-dev < > cfe-dev at lists.llvm.org> wrote: > > To explain to others who didn't follow that thread: > > GDB currently does something amazingly stupid (and has since i wrote it) > to find the RTTI type. There were no other good options

...ocal storage needs. IIRC thread_local is not implemented across all the platforms that llvm support. If the idea is to improve libcxxabi's demangler, then it should be straightforward to use these functions instead of thread_local. [1] https://github.com/llvm-mirror/libcxxabi/blob/master/ src/cxa_demangle.cpp [2] https://github.com/llvm-mirror/llvm/blob/master/lib/Demangle/ItaniumDemangle.cpp [3] https://github.com/llvm-mirror/libcxx/blob/master/ include/__threading_support PS: Here's a particularly amusing bug of the current libcxxabi demangler: https://bugs.llvm.org//show_bug.cgi?id=31031 C...

...clang doesn't even need a demangler. > llvm tools, lld, and compiler-rt do. libc++abi provides a full C++ demangler, along with an extended API that provides a tree-based representation of the demangled name (implemented for LLDB). http://llvm.org/viewvc/llvm-project/libcxxabi/trunk/include/cxa_demangle.h?revision=HEAD&view=markup On Jul 4, 2012, at 10:08 PM, Chandler Carruth wrote: > In the same way that the core LLVM libraries have support routines for DWARF, I think that both mangling and demangling should be provided as well. You can't really implement mangling without a full C+...

..., it might be interesting to try to replace the > FastDemangle.cpp demangler in LLDB with this, to restore the one > true demangler in the source tree. The FastDemangler.cpp is only > partially completed, and calls out to ItaniumDemangle.cpp in llvm > (which is a copy of cxa_demangle.cpp) if it fails to parse the symbol. > > Any thoughts here would be appreciated! > Thanks, > Erik > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org&g...

...building fuzz > target with regular flags (no coverage). > 2. There should also be a bot that actually runs continuous fuzzing. > Our buildbots are not suitable for this, so I was planing to add the llvm > fuzzers to OSS-Fuzz (https://github.com/google/oss-fuzz) > We already run the cxa_demangler fuzzer there with quite a bit of success. > clang-fuzzer is now running on oss-fuzz, and here are two trophies so far: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3134 ASSERT: ParmVarDeclBits.ScopeDepthOrObjCQuals == scopeDepth && "truncation!" (haven't seen...

...bc++. However, we simplified it to make it more portable. The simpifications naturally led to the ability to remove the arena allocation routines. The copy in libc++ needs to retain a certain amount of flexibility due to the exporting of the interface into the user's address space (via the __cxa_demangle interface). However, making adjustments that improve performance in the LLVM version should be acceptable. > >> >> > FYI when I said 14+% (and now it's 17%), I mean the overall performance >> of starting lldb, not just the demangler itself. It's probably several...

Hi, As a part of a recent move of libFuzzer from LLVM to compiler-rt I am looking into updating the build code for the libraries which use libFuzzer. I have tried to compile llvm-mc-assemble-fuzzer, and llvm-mc-disassemble-fuzzer, and I couldn’t build either of those. For the first one, the reason is that it refers to a nonexistent enum, and for the second one I believe the reason is that it

...ler. > > llvm tools, lld, and compiler-rt do. > > libc++abi provides a full C++ demangler, along with an extended API that > provides a tree-based representation of the demangled name (implemented > for LLDB). > http://llvm.org/viewvc/llvm- > project/libcxxabi/trunk/include/cxa_demangle.h?revision=HEAD&view=markup > > > On Jul 4, 2012, at 10:08 PM, Chandler Carruth wrote: > > In the same way that the core LLVM libraries have support routines for > DWARF, I think that both mangling and demangling should be provided as > well. > > You can't rea...

On Wed, Jul 4, 2012 at 8:33 AM, Alexey Samsonov <samsonov at google.com> wrote: > Hello! > > We want to implement in-process symbolizer for {Address,Thread}Sanitizer > testing tools that would be based on LLVM libraries. > I've noticed that llvm-nm (as well as other tools) doesn't demangle C++ > names. Is it true, that LLVM doesn't have the code that is capable

..., it might >> be interesting to try to replace the FastDemangle.cpp demangler in LLDB with >> this, to restore the one true demangler in the source tree. The >> FastDemangler.cpp is only partially completed, and calls out to >> ItaniumDemangle.cpp in llvm (which is a copy of cxa_demangle.cpp) if it >> fails to parse the symbol. >> >> Any thoughts here would be appreciated! >> Thanks, >> Erik >> >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> http://lists....

We are trying out lld ELF on windows. It works great, but a big difference from running it on linux is that it cannot demangle c++ names since there is no itanium demangler available on windows. We have an implementation in libcxxabi/src/cxa_demangle.cpp. I see that there was some discussion about having a version of that in lib/Support, but I don't think a patch was ever posted. So, some questions * Is having an itanium demangler in lib/Support something people find desirable or at least acceptable? * The libcxxabi code is dual licensed...

Hello! We want to implement in-process symbolizer for {Address,Thread}Sanitizer testing tools that would be based on LLVM libraries. I've noticed that llvm-nm (as well as other tools) doesn't demangle C++ names. Is it true, that LLVM doesn't have the code that is capable of that, and if yes, are there any plans to add it? Depending on something like libiberty.a doesn't seem like a

well, top-of-branch lldb uses this code, that's how I found it. Do you mean libc++'s demangler? FYI when I said 14+% (and now it's 17%), I mean the overall performance of starting lldb, not just the demangler itself. It's probably several times faster now with this change (https://reviews.llvm.org/D32500) On Tue, Apr 25, 2017 at 12:19 PM, Vedant Kumar <vsk at apple.com>

...like to get through. After that, it might be interesting to try to replace the FastDemangle.cpp demangler in LLDB with this, to restore the one true demangler in the source tree. The FastDemangler.cpp is only partially completed, and calls out to ItaniumDemangle.cpp in llvm (which is a copy of cxa_demangle.cpp) if it fails to parse the symbol. Any thoughts here would be appreciated! Thanks, Erik -------------- next part -------------- commit e526dffc812b303734fbce5644f2d2ae4c4ca3dc Author: Erik Pilkington <erik.pilkington at gmail.com> Date: Thu Jun 15 13:23:08 2017 -0700 demangle tre...