debugging wine

Open forum for end-user questions about Wine. Before asking questions, check out the Wiki as a first step.
Forum Rules
Locked
noodlez
Newbie
Newbie
Posts: 1
Joined: Fri Dec 05, 2008 3:22 pm

debugging wine

Post by noodlez »

What im trying to do is step through wine from the before the load process up until the load process to understand asm better, i can't manage to set a breakpoint on _start nor any existance of main, so i really want to see wine from the beginning till the end step by step. if any one can tell me where to break i'd really appreciate it!!
vitamin
Moderator
Moderator
Posts: 6605
Joined: Sat Feb 23, 2008 2:29 pm

Re: debugging wine

Post by vitamin »

noodlez wrote:What im trying to do is step through wine from the before the load process up until the load process to understand asm better, i can't manage to set a breakpoint on _start nor any existance of main, so i really want to see wine from the beginning till the end step by step. if any one can tell me where to break i'd really appreciate it!!
It would probably take you several days if not weeks to do that...
Wine's startup sequence is complicated you can read about that in dev's manual: http://www.winehq.org/site/docs/winedev ... IALIZATION

BTW that part is outdated and does not include wineboot, winedevice and explorer.
infinity-909
Level 1
Level 1
Posts: 5
Joined: Mon Apr 23, 2012 2:53 pm

Post by infinity-909 »

Trying to set breakpoints at process start I stumbled across this thread.

I've got a Windows program which calls several other programs in the course of its execution.

Is there really no easy way to stop software consisting of several executables between two executable calls?
infinity-909
Level 1
Level 1
Posts: 5
Joined: Mon Apr 23, 2012 2:53 pm

Post by infinity-909 »

Setting a breakpoint at CreateProcessW seems to solve the problem. Are there any objections to this method? Is there any way to display this function's arguments in winedbg? Having winedbg and WINEDEBUG=+relay output is a lame workaround.
Locked