similar to: How to compile Wine without debugging symbols

On Sat, Dec 15, 2018 at 12:02 PM Vedant Kumar via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi, > > > On Dec 15, 2018, at 10:32 AM, Brian Gesiak via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > Hello all! > > > > I find that using lldb to debug LLVM libraries can be super > > frustrating, because a lot of LLVM classes, like

Hi Andy, I haven't tested this on Linux, but on MacOS the RuntimeDyldMemorManager::getSymbolAddressInProcess method should find symbol addresses in the host program, including symbols from static archives linked into the program. However, one gotcha is that the symbol has to be reachable from main, otherwise the linker may strip it from the final executable. Do you have a test-case that I

Hi Andy, I think that makes sense. I'm currently rewriting the core Kaleidoscope tutorials - I'll look at adding support for this. - Lang. On Fri, Aug 14, 2015 at 7:38 AM, Andy Somogyi <andy.somogyi at gmail.com> wrote: > After some fiddling with it, it does in fact look like it works as you > describe Lang. > > The trick was you had to call > >

My Wine build is lacking debug symbols. I tried to compile it Code: ./configure and Code: CFLAGS="-g" ./configure but it didn't help. How to compile wine with debug symbols or maybe is there a ready package? I use openSuSE 11.1 x86_64.

I'm cross-compiling for MIPS. The test-case is as simple as it can be: void foo() {} $clang -target mips64-octeon-linux -c -B path/to/cross/compiled/mips/assembler a.c And then I look at the object file: $ nm a.o 0000000000000020 t $tmp0 0000000000000000 T foo I would like to know what "$tmp0" is. Furthermore, if I pass -g to clang, I see a whole bunch of such symbols. Some of

Hi, I'm trying to debug an R interface to a Fortran subroutine from Windows. (Yes, I know I should try Unix/Linux as well, but a quick attempt suggested that the (MinGW g77) Fortran compiler I have installed on my Windows laptop works better on this Fortran code.) I'm trying to follow the instructions in the "Writing R Extensions" Manual: Start R under the debugger after

Hi, I'm trying to debug an R interface to a Fortran subroutine from Windows. (Yes, I know I should try Unix/Linux as well, but a quick attempt suggested that the (MinGW g77) Fortran compiler I have installed on my Windows laptop works better on this Fortran code.) I'm trying to follow the instructions in the "Writing R Extensions" Manual: Start R under the debugger after

Lang, I added the add/get global mapping to my kaleidoscope JIT, but I think perhaps these would make more sense if they were added to the object linking layer as they would be generally usable there. On Aug 19, 2015, at 11:19 PM, Andy Somogyi wrote: > Hey Lang, > > I've added this to my Kaleidoscope JIT, and it seems to work just fine, basically I copied the global mapping

Hello, I'm interested in debugging code JITted by LLVM at runtime. For that, I should naturally have some way to emit DWARF that faithfully describes the JITted code into memory along with the JITted code itself and point the debugger to it. Let's assume that the bridge with the debugger is taken care of (e.g. http://llvm.org/docs/DebuggingJITedCode.html) - my concern in this question is

    Hello all,     I develop a project based on Clang where I need to read all symbols from a library. For symbols libraries (.a/.lib) I use the following code:     auto &FM = C->getFileManager();     ...     auto Buffer = FM.getBufferForFile(FileEntry);     ...     auto Object = llvm::object::ObjectFile::createObjectFile(Buffer);     This code crashes at the last line if the file in

It seems that llvm-ld is stripping debugging symbols even with optimizations disabled: > cat main.c int main() { int a = 42; return a; } > clang -c -g -emit-llvm -o main.bc main.c > llvm-ld -disable-opt -b=a.out.bc main.bc > clang -g a.out.bc -o a.out >gdb a.out [...] (gdb) break main Breakpoint 1 at 0x40045b:

Hello, I'm writing an R package that is mainly written in C++. By default, R CMD INSTALL creates C/C++ flags as follows: -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -g However, my package is fairly large. With debug info compiled into the library, the generated .so file is over 200MB. Without debug info, it's about 30MB. I hope

On 23 November 2010 18:03, Bagel <bagel99 at gmail.com> wrote: > Would someone be so kind as to tell me what the status of debugging symbols > (DWARF) generated by clang/llvm is? Hi Bagel, It should be fairly complete... > When I generate an executable with "clang -g" followed by "llc -O0" and feed it > to gdb, I get "no debugging symbols found".

On Sat, Dec 15, 2018 at 9:37 PM Chandler Carruth <chandlerc at gmail.com> wrote: > > On Sat, Dec 15, 2018 at 6:13 PM Davide Italiano <davide at freebsd.org> wrote: >> >> On Sat, Dec 15, 2018 at 12:02 PM Vedant Kumar via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >> > >> > Hi, >> > >> > > On Dec 15, 2018, at 10:32

Hi Everyone -- I'm planning on using LLVM to add some optimizing compiling capability to a Byte-Code driven virtual machine that is part of my foundation platform for a series of tool products I am building. I'm still pretty new to this whole arena and am in particular curious about one important aspect: It strikes me that the more optimizations applied to code (whether at the source

Would someone be so kind as to tell me what the status of debugging symbols (DWARF) generated by clang/llvm is? I am on a linux x86-64 system (Fedora 13). Is gdb supposed to understand the generated DWARF? When I generate an executable with "clang -g" followed by "llc -O0" and feed it to gdb, I get "no debugging symbols found". What is the status of lldb on

Hello! I'm having some problem compiling llvm 2.1 for macports. I'm getting errors from some undefined symbols. What am I doing wrong? I couldn't find anything on the website or the mailing list. Thanks. > cd "/opt/local/var/macports/build/_Users_Shared_erickt_Projects_macports-trunk_dports_lang_llvm/work/build" && ../llvm-2.1/configure --enable-optimized

https://bugs.freedesktop.org/show_bug.cgi?id=56535 Priority: medium Bug ID: 56535 Assignee: nouveau at lists.freedesktop.org Summary: Resident evil 4 with wine: crash Severity: critical Classification: Unclassified OS: Linux (All) Reporter: king.infet at gmail.com Hardware: x86 (IA32) Status:

Dear plotting experts, I simply can't figure out how I can force bwplot to print mathematical symbols in the strips. Example: x <- rnorm(30) lab <- factor(c(rep("one", 10), rep("two", 10), rep("three", 10))) bwplot(~ x | lab) gives labels "one", "two", "tree" but I would like to change this into expression(lambda == 1),

Hi Björn, I'm not sure I understand what you are actually trying to achieve. Do you want to be able to debug from your main code, and step into the JITed code? Do you want to be able to set breakpoints, list callstacks, etc in the JITed code? Do you want to, from a crash, identify where in your JITed code it went wrong? The first two are definitely one or more order(s) of magnitude harder