similar to: Getting debugging symbols into the backtrace

Hello, We just started using WineLib, and have very basic question: which -g??? option do you use to do source level debugging with winedbg? I searched the documentation and mailing list for any step-by-step about this, but found nothing. So either the answer is so obvious that I just can't see it - or it doesn't work? By default, winemaker seems configure things for no debug - so

Hi, If you saw this topic => http://forum.winehq.org/viewtopic.php?t=12633 F.E.A.R.3 crash on startup when i launch it. This is my crash log : http://pastebin.com/38qKqEKh The problem is that i haven't got a "proper" backtrace when F.E.A.R.3.exe crash. So, i tried to get a backtrace with winedbg. Like F.E.A.R.3.exe crash very quickly, i launch these command : Code: wine

Hi Florian, Thanks for the reply. On Fri, Dec 8, 2017 at 6:48 PM, Florian Hahn <florian.hahn at arm.com> wrote: > Hi, > > On 08/12/2017 06:24, Nagaraju Mekala via llvm-dev wrote: >> >> Hi all, >> >> I am new to LLVM. Currently working on adding an embedded target to >> LLVM backend. >> I was able to generate the object file for our

Hi! I'm trying to install the Longman Dictionary of Contemporary English (which I have got with the book with the same name). I'm running: the latest wine release (20020228) Redhat 7.2 gcc 2.96-98 fake windows dir (altough I have tried it with a win98 install a month ago) The installer is an installshild with win16 libs. When I run it, it puts up a message box, that the install files

On Sep 10, 2009, at 10:48 AM, Devang Patel wrote: > Hi All, > > Today, debugging information is encoded in LLVM IR using various > llvm.dbg intrinsics, such as llvm.dbg.stoppoint. For exmaple, Right. > This approach has several disadvantages. > - The llvm.dbg.stoppoint()s act like hurdles to the optimizer. The > LLVM customers expect that the optimizer does not trip over

Hi all, I have a helpdesk ticketing system app called Onyx that the company requires me to use. It doesn't install, and isn't listed in AppDB. If I run the installer with "WINEDEBUG=+loaddll,warn+all" I get this error: fixme:odbc:SQLConfigDriver ((nil) 1 "SQL Server" (null) 0x7e4ad4fc 300 0x7e4ad4fa) trace:loaddll:free_modref Unloaded module L"c:

Hi, I've been experimenting with the CodeExtractor class and have been running into a problem where the verifier pass fails with the error "function-local metadata used in wrong function" when I compile with debugging symbols enabled (-g flag). The issue seems to be that after extraction we have metadata that references variables that aren't allocated in the extracted function.

Well, I am much happier now that I understand about dsymutil, and can actually step through my program in gdb. However, there are still some issues that are puzzling me. 1) First off, the debugger appears to stop at odd points. The IR for my main function looks correct to me: define i32 @"main(tart.core.Array[tart.core.String])->int"(%"tart.core.Array[tart.core.String]"*

Hello, Argiris > Can you please try out the steps I mentioned before with the linux > binaries ? I just want to make sure that there's not something wrong > with my setup. Here they are: $ cat dbg.c int main() { return 0; } $ gdb a.out GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

On Sep 10, 2009, at 10:48 AM, Devang Patel wrote: > The proposed solution is to optionally attach debug information with > llvm instruction directly. A new keyword 'dbg' is used to identify > debugging information associated with an instruction. The debugging > information, if available, is printed after the last instruction > operand. The debugging information entry uses

Hi All, Today, debugging information is encoded in LLVM IR using various llvm.dbg intrinsics, such as llvm.dbg.stoppoint. For exmaple, !1 = metadata !{i32 458769, i32 0, i32 12, metadata !"foo.c", metadata !"/tmp", metadata !"clang 1.0", i1 true, i1 false, metadata !"", i32 0} ... call void @llvm.dbg.stoppoint(i32 5, i32 5, metadata !1) store i32

Hi y'all: Is this a X11DRV problem? This happens on a RedHat 7.2 installation of a friend who is in Turkey and has no usenet access. So I'm posting in behalf of him. He is running a 16-bit VB3 application and the debugger shows up with this unhandeled exception as soon as he acceses the program's search function. However he can "cont" and the program behaves fine

Hi, Taking a break for a few minutes from my fst/jack_fst work I decided to try a quick install of Myst, an old game that has, at various times, installed, not installed, worked or not worked with Wine. (According to the app database.) Anyway, I wanted to try it out so, to cause as few problems as possible for my existing Wine installation, I created a new user account named myst and then

Hi, I am planning to use LLVM for a compiler validation project that checks if the optimized version of the code is the correct translation of the unoptimized code. And I have a couple of questions. I need two pieces of information from the compiler: 1) Some kind of mapping between the structure of the unoptimized and optimized code. It seems, that can be obtained via the llvm.dbg.stoppoint

When I generate debug information for a source file that has a number of static functions that are unused, all of the debugging metadata that I generated for them during initial compilation remains even after the source function definitions have been stripped out of the IR. (e.g. in the MD for DW_TAG_compile_unit's list of subprograms, each of those functions' info is still in the list,

I created a brand new nt 4.0 server with exchange 5.5 server in my samba 3.0 pdc domain with no problems. The exchange server runs fine under the samba 3.0 pdc, but when I try to install exchange 5.5 sp4 on the exchange server the service pack gives me an Dr. Watson error. The exchange service pack makes it through the copying of the service pack files and then modifies the registry settings for

On 24 April 2012 16:04, Matt Pharr <matt.pharr at gmail.com> wrote: > When I generate debug information for a source file that has a number of static functions that are unused, all of the debugging metadata that I generated for them during initial compilation remains even after the source function definitions have been stripped out of the IR.  (e.g. in the MD for DW_TAG_compile_unit's

On 2009-09-10 20:48, Devang Patel wrote: > Now, the optimizer does not need to worry about those llvm.dbg > hurdles. Instructions do not lose their location information when they > are rearranged in instruction stream. And the stage is set to produce, > preserve and emit accurate debug information for inlined functions. > > Any thoughts/suggestions/questions ? > Sounds

Hi im trying to use an application on MsAccess , first a try to open a single mdb and i get: wine Access\ 97\ Runtime/Msaccess.exe "c:\Informes.mdb" fixme:font:SetMapperFlags (0x224, 0x00000001): stub - harmless fixme:ole:CoRegisterMessageFilter stub fixme:ole:DllDebugObjectRPCHook stub fixme:ole:MSFT_ReadValue BSTR length = -1? fixme:ole:ITypeInfo_fnAddressOfMember (0x7e93ecc8) stub!

Hi is possible to run an application twice at the same time? I have an access 97 app. First time i run it perfect, but i would like to run it again without closing the first one. it crashes the output is trace:loaddll:load_builtin_dll Loaded module L"kernel32.dll" : builtin trace:loaddll:load_builtin_dll Loaded module L"c:\\windows\\system\\advapi32.dll" : builtin