similar to: Wine debug sumbols. How to get?

I have Opensuse 11.0. Using icewm. When I run winecfg or any windows application it freezes in 1 minutes. Why? PS: Computer is not freezing.

Hi! I have iBook G4, I was installed on this openSuSe 11.1 ppc, and I whant to install wine 1.0.1. In the whine repositories no wine for ppc architecture. I downloaded source tar.bz2 file, configuring finished succesed, but compiling, when process with file dlls/mshtml.tbl, exiting with error: error: get_type_vt: unknown type: 0x2b. Hou fix it :(

Hi, I'm trying to recover the inheritance relations for a class type (so a list of base classes) from a llvm ir file generated via compiling some cpp file using clang. I have access to the TypeSymbolTable and have found the class type I want to know the base classes for in the table. How do I go about extracting this (debug) information? I'm stuck here: if(StructType*

Hello Everyone, I have general question WRT llvm.dbg.value intrinsic function semantics. Under what circumstances should a frontend choose to emit(at -O0(No optimization)) llvm.dbg.value for a local variable. I saw some debuginfo code in flang(older one), sort of it choose to emit *llvm.dbg.value* for *every load operation* happening on a *local variable*. And as noted below in IR snippet it

Thanks Eric, but could you give me a little bit more hints or pointers please? I looked into DebugInfo.h, but I'm still not sure how to start. It sounds like I'd have to somehow manually extract metadata nodes from an instruction. Thanks, JS On Wed, Jan 22, 2014 at 10:14 PM, Eric Christopher <echristo at gmail.com>wrote: > This is likely going to be difficult if possible. I

Hi, For my project, I am using internal llvm class functions to print the filename and directory associated with an instruction from the debug information. With a recent checkout of llvm and clang (svn revision 129445), the following custom code (e.g. in a pass that prints directory info for all instructions) returns the filename iso. directory whenever Scope refers to a lexical block: if (const

Hopefully somebody has info on this topic. I have just installed Wine on OpenSuse 11.1. I've tried to install MSOffice 2003 but when double clicking on setup.exe nothing happens. I also tried by typping "wine /media/MSOfficeCD/setup.exe" but I get this error X Error of failed request: XF86VidModeExtensionDisabled Major opcode of failed request: 135 (XFree86-VidModeExtension)

Hello, I use llvm and llvm-gcc as a C-to-C transformation tool using a modified version of the c backend, and rely on llvm debug instructions to link back to the original source code. Does anyone know how to get detailed line number and variable debug information at optimization levels beyond O0? Currently, I extract this debug information by compiling with -g. This works fine with

On Mon, Nov 8, 2010 at 9:56 AM, Devang Patel <dpatel at apple.com> wrote: > > On Nov 6, 2010, at 7:35 PM, Talin wrote: > > After to speaking to Devang and a number of other people at the developer's > conference, I was able to make some forward progress on getting debugging to > work. I'm now able to actually single-step through my program and set > breakpoints,

Dear Staff, I am asking this question: given a line of IR code in *.ll file, how can I know the corresponding line number and C/C++ source file name for this IR code? I am investigating some code patterns with LLVM IR, I need to know where this IR code come from (the line number in a source file name). An existing way is using -g option to compile my software, then I can

Hi, I have bitcode files built by LLVM v3.3 and need to process them using v3.4 tools. While I don't expect a lot of backward compatibility in LLVM, luckily it seems everything's working fine, except for reading source line information attached to instructions. I use this piece of code [0] to get source line information. For v3.4, instruction.getMetadata returns NULL. I used llvm-dis to

Hi, Following is a proposal to improve location coverage for Function parameters in LLVM. The patches for review will be posted soon. RFC: [DebugInfo] Improving Debug Information in LLVM to Recover Optimized-out Function Parameters Ananthakrishna Sowda(Cisco), asowda at cisco.com Nikola Prica (RT-RK/Cisco), nprica at rtrk.com Djordje Todorovic(RT-RK/Cisco), djtodorovic at rtrk.com Ivan Baev

Thank you for your interest and comments! Please see my responses inline. On 2/7/19, 3:17 PM, "aprantl at apple.com on behalf of Adrian Prantl" <aprantl at apple.com> wrote: > On Feb 7, 2019, at 1:49 PM, Ananthakrishna Sowda (asowda) via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi, > Following is a proposal to improve location

On Thu, 2011-01-06 at 11:13 -0800, Devang Patel wrote: > On Jan 4, 2011, at 7:32 PM, Jacob Zimmermann wrote: > > > Hi, > > > > I'm currently porting some code from LLVM 2.6 to 2.8 and need to be able > > to extract the debug info produced by LLVM-GCC and stored in the > > compiled .bc file. However I admit I'm slightly confused about how > >

Currently there is a series of patches undergoing review[0] that seek to enable the use of multiple IR/MIR values when describing a source variable's location. The current plan for the MIR is to add a new instruction, DBG_VALUE_LIST, that supports this functionality by having a variable number of operands. It may be better however to simply replace the existing DBG_VALUE behaviour entirely

On Nov 8, 2010, at 10:52 PM, Talin <viridia at gmail.com> wrote: > On Mon, Nov 8, 2010 at 9:56 AM, Devang Patel <dpatel at apple.com> wrote: > > On Nov 6, 2010, at 7:35 PM, Talin wrote: > >> After to speaking to Devang and a number of other people at the developer's conference, I was able to make some forward progress on getting debugging to work. I'm now

Thanks. Note that there are still a few references to this MDNode scattered throughout the code-base, so if it's no longer being generated, there may be some bugs lurking there. Eli From: Devang Patel [mailto:dpatel at apple.com] Sent: Thursday, February 09, 2012 19:36 To: Bendersky, Eli Cc: llvmdev at cs.uiuc.edu Subject: Re: generating !llvm.dbg.sp On Feb 9, 2012, at 7:17 AM,

After to speaking to Devang and a number of other people at the developer's conference, I was able to make some forward progress on getting debugging to work. I'm now able to actually single-step through my program and set breakpoints, and examine function parameters. However, I'm also seeing a lot of new problems which weren't exposed before. After spending the better part of two

Hi all, I used to extract the debug information from an LLVM Instruction in the following way: if (MDNode *N = I->getMetadata("dbg")) { // Here I is an LLVM instruction DILocation Loc(N); // DILocation is in DebugInfo.h unsigned Line = Loc.getLineNumber(); StringRef File = Loc.getFilename(); StringRef Dir = Loc.getDirectory(); } As specified also at

Thanks Eric. I know some of the references are in the code used for backward compatibility. - Devang On Feb 13, 2012, at 9:21 AM, Eric Christopher <echristo at apple.com> wrote: > Thanks. I'll get them. :) > > -eric > > On Feb 13, 2012, at 1:41 AM, Bendersky, Eli wrote: > >> Thanks. Note that there are still a few references to this MDNode scattered throughout