similar to: Winedbg on FreeBsd Question

Hi, Using WineDbg, I have problems to attach to a process. I start "winedbg". then "walk process". It gives reference to a W-process. Trying attach to this process gives me error 5. Where could i find more info on these error numbers ? [syl@snoop La 4?me Proph?tie]$ winedbg WineDbg starting... on pid 0 Wine-dbg>walk process pid threads parent exe 0806ba80

Hi, I have discovered i can run starcraft at (almost) full speed on my system. This only works one time, directly after reboot. When tried a second time it's all choppy again. My guess is there're some stale wine processes after the first attempt. When i reboot and start wine instead of winedebug the game video performance is choppy. When i start the game with winedbg after that The

Hi list, updating wine to current cvs shows that stg could be broken in winedbg. Running programs that crash and go to debugger make winedbg jump nowhere in winedbg's data. This happens with several programs I tested (windows / dos programs), and the backtrace is always the same. The programs all complain about a read access fault at 0x0815cbe4 (yes, always the same adress) and show this

Hello, With wine-20010326 breakpoints doesn't seem to work. Did anyone else experienced this or am I doing something wrong? I did the following: $ winedbg setup.exe Wine-Dbg> break FindResourceA Wine-Dbg> continue The application runs as there were no breakpoints set, calls the function with the breakpoint several times without stopping on it. After the application ends winedbg

As this happens with all applications, I just tried an rpm, it's a bit old (20020709), but works fine. > > --- "puoti@inwind.it" <puoti@inwind.it> wrote: > > When I run any program with wine I get this output: > > $wine myapp.exe > > wine: Unhandled exception, starting debugger... > > err:seh:start_debugger Couldn't start debugger > >

When I run any program with wine I get this output: $wine myapp.exe wine: Unhandled exception, starting debugger... err:seh:start_debugger Couldn't start debugger ("debugger/winedbg 134682584 28") (2) Read the Wine Developers Guide on how to set up winedgb or another debugger what can I do?

i did some of RTFM and didn't find an answer to my question: is it possible to do %Subject% (i mean threads of wine-process)? "attach wpid" puts me on the main thread: Wine-dbg>walk proc pid threads parent executable >00000016 3 00000014 'C:\windows\system\msiexec.exe' Wine-dbg>walk th process tid prio 00000016 (D)

I just upgraded to Ubuntu jaunty. I've been using the Intrepid Wine repo before, then I updated my sources.list for Jaunty. All wine programs including winecfg itself throws tons of error now upon initial startup: Code: fixme:dbghelp_dwarf:compute_location Unhandled attr op: e0 dwarf.c:1355: dwarf2_parse_variable: Assertion `subpgm->func' failed. wine: Assertion failed at address

Wine debug no longer launches for me. Not that I know how to use it, but I like trying to find and report bugs. Warning: /usr/bin/winedbg.exe not accessible from a DOS drive Warning: /usr/bin/winedbg not accessible from a DOS drive Warning: /usr/bin/winedbg 137011720.exe not accessible from a DOS drive Warning: /usr/bin/winedbg 137011720 not accessible from a DOS drive Warning: /usr/bin/winedbg

Hello Wine users! I've got a minidump from a ("real") Windows user of our game and would like to extract information from it using winedbg. The information winedbg gives me by default, is this: WineDbg starting on minidump on pid 068c warzone2100.exe was running on #1 Intel ???-0.521 CPU on Windows XP (2600) Register dump: CS:001b SS:0023 DS:0023 ES:0023 FS:003b GS:0000

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 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!

Hello, we're the developers of a large 64-bit Windows application that uses Wine 1.3.0 64-bit on Linux. When testing began we discovered several crashes inside our windows code on startup and needed to debug them. But the problem seems to be getting any kind of stack trace information from the 64-bit winedbg. This used to work with the 32-bit version of winedbg. Even if I write a 64-bit

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

I have an application with acces97, after some weeks trying to execute it, i got it! but now when the i try to do some function it crashes. i think that the problem comes when the application try to call shell, but im not sure. the code when i click on the button is: Public Sub EjecutaAccessOLD(ByRef MiAccess As Object, vista As Integer, Informe, Condici?nWhere As String) Dim strDB As

running winedbg manually to debug a program, it says that an adress is invalid when trying to set breakpoints. here is my cmdline: $ winedbg iexplore.exe (happens with all programs) fixme:console:SetConsoleCtrlHandler (0x403a1d30,1) - no error checking or testing yet WineDbg starting on pid 84509d8 Breakpoint 1 at 0x00401ee6 Invalid address, can't set breakpoint You can turn on deferring

A) DON'T EVER RUN WINE AS ROOT! B) What version of wine? C) Remove ~/.wine (and probably /root/.wine) and try again. If you still have problems, post back. -Austin On 8/6/07, lalev@uni-svishtov.bg < lalev@uni-svishtov.bg> wrote: Hi everyone, This happens every time I start winedbg, no matter what program I want to debug. It's ubuntu feisty fawn and I have built wine from sources.

Hello, I've used app-emulation/wine-0.9.7 with ie6, installed by ies4linux. All worked fine! (Except of that I've never succeeded in writing hebrew...) I've upgraded to app-emulation/wine-0.9.8-r1, ie6 stopped displaying Hebrew pages. I've also noticed that the View->Encoding menu is empty, it should contain a lot of code pages. I also get the following trace:

Hi there, i'm gettin trouble with an ultima online client.. i'm sure that this client works with wine, because I evere played with it.. now, after the new installation of linux i'm getting this error: [blink@plasma - 10:41 - ~/.wine/fake_windows/Program Files/Ultima Online 2D] [$ -> wine tmclient.exe Invoking /usr/lib/wine/wine.bin tmclient.exe ... Please use the registry key

I wanted to try how fast will World of Warcraft run on my new AT3N7A-I motherboard. Installed kubuntu 9.10, wine 1.1.40 from PPA, copied working World of Warcraft directory from another machine (where it works just fine under wine), removed configuration files and started wine ./Wow.exe -opengl. Unfortunately I've got the next message after Wow.exe loaded necessary files and tried to