search for: debuggee

...: jmp 0x40373096 _CheckNotSysLevel+0x22 [/home/david/wine-20041201/dlls/kernel/syslevel.c:183] in kernel32 1283 static inline void WINAPI DbgBreakPoint(void) { __asm__ __volatile__("int3"); } Wine-dbg> then when I tried to copy that, <sob> habit bit. Ctrl-C: stopping debuggee err:seh:setup_exception nested exception on signal stack in thread 003b eip ffffe000 esp 40018c28 stack 0x40610000-0x40710000 Questions: 1. Should I take a step back and throw out the dlls I moved to the system folder, or should I add the dlls to config? Yes, I know that I'm not supposed to...

...39;. 'debug' offers: ? a visible code window with line-numbered code and highlighted execution point; ? the ability to set (conditional) breakpoints in advance, at any line number; ? the opportunity to keep going after errors; ? multiple debugging windows open at once (when one debuggee calls another, or itself); ? full debugging of 'on.exit' code; ? the ability to move the execution point around without executing intervening statements; ? direct interpretation of typed-in statements, as if they were in the function itself. For further information on 'debug...

...'browser', offering: * a visible code window with line-numbered code and highlighted execution point; * the ability to set (conditional) breakpoints in advance, at any line number; * the opportunity to keep going after errors; * multiple debugging windows open at once (when one debuggee calls another, or itself); * full debugging of 'on.exit' code; * the ability to move the execution point around without executing intervening statements; * direct interpretation of typed-in statements, as if they were in the function itself. See R-news 3.3 for an article on using...

...39;. 'debug' offers: ? a visible code window with line-numbered code and highlighted execution point; ? the ability to set (conditional) breakpoints in advance, at any line number; ? the opportunity to keep going after errors; ? multiple debugging windows open at once (when one debuggee calls another, or itself); ? full debugging of 'on.exit' code; ? the ability to move the execution point around without executing intervening statements; ? direct interpretation of typed-in statements, as if they were in the function itself. For further information on 'debug...

...'browser', offering: * a visible code window with line-numbered code and highlighted execution point; * the ability to set (conditional) breakpoints in advance, at any line number; * the opportunity to keep going after errors; * multiple debugging windows open at once (when one debuggee calls another, or itself); * full debugging of 'on.exit' code; * the ability to move the execution point around without executing intervening statements; * direct interpretation of typed-in statements, as if they were in the function itself. See R-news 3.3 for an article on using...

...to me) i get the standart-msg (single stepping until...) and then nothing else. When i look at the processes wine-preloader is sleeping (vm-size 1.5gb!!!) and a sub-process with the same name is stopped (around 1.1gb!!!). If i break the debugging with ctrl-c i get these lines: Ctrl-C: stopping debuggee First chance exception: ^C in 32-bit code (0x0069956e). Register dump: CS:0073 SS:007b DS:007b ES:007b FS:003b GS:0033 EIP:0069956e ESP:7fbff814 EBP:7fbffed8 EFLAGS:00000302( - 00 - -IT1) EAX:7ced5c1f EBX:7fc94d7c ECX:7ced5c1f EDX:7ced5cc3 ESI:7ffdeea0 EDI:00001000 Stack dump: 0x7fbff814...

...before .GlobalEnv and the rest of the search path, but it is NOT assigned to unless specified explicitly in "assign". It seems to me that it would be simple to add this feature in R. One particular area where it would be useful: I have a debugger for S, which makes a modified copy of the debuggee function in frame 0. This means that the original isn't modified. In the R version of the debugger, I have to overwrite the original function, and there is a risk that I'll call "save.image" or similar with the modified debug version being saved inadvertently, losing the original...

...in the docs/misc/ folder: set debug=y in Config.mk, crash_debug=y in xen/Rules.mk I also added -fno-omit-frame-pointer to these file as well. I compiled with no errors and booted with minicom connected to the workstation via com1 but when I do Ctrl-A three times to connect, nothing happens. The debuggee boots find and gives me the login screen as normal. Is there a special time to hit the Ctrl-A in minicom? Should the kernel wait for a connection from gdb? I''ve tried various combinations of using nsplitd and a serial-split patch I found mentioned on mailing lists and setting the boot fl...

Hi, Whenever I type ?, ?, or ?, etc., Wine crashes immediately before displaying the letter. It doesn't have enough time to display any debug message neither. Dom

...o install a hook that gets executed on every line, call, return, def, etc. and runs a fair bit of conditional code on it (tracing the stack frames, checking for breakpoints, etc.). The reason that it is unuseably slow with rails is that there are a LOT of statements to process in this way until the debuggee code gets hit. I played around with it and came up with a way of starting the debugger only just before it is required - similar to adding "breakpoint" calls to my code, I can now say "start_debug", which will then break into the core ruby debugger in the console where WEBrick...

...8 0x404dfd62 ExitProcess in kernel32 (0x406cfe90) 9 0x405c4228 __wine_exe_main in rundll32 (0x406cff20) 10 0x404e56a2 start_process in kernel32 (0x406cfff4) 11 0x40031de1 wine_switch_to_stack in libwine.so.1 (0x00000000) 0x40ebebea: movl 0x0(%eax),%eax Wine-dbg> Ctrl-C: stopping debuggee WineDbg terminated on pid 0x8 err:seh:setup_exception nested exception on signal stack in thread 0009 eip ffffe40e esp 401efb8c stack 0x405d0000-0x406d0000 wine client error:9: write: Bad file descriptor Any hints? Thanks! Thomas

Hello, I have been struggling with WinDbg/Kd for the last week, but to no avail... So I finally decided to ask here. Basically, I am using a Windows XP virtual machine (thanks to VMWare6) and wanted to do some kernel debugging using Windbg. So, I did configure everything from the virtual machine side (using this guide: http://silverstr.ufies.org/lotr0/windbg-vmware.html), and then tried my hands

...t32.dbg ("") err:dbghelp:pe_load_dbg_file -Unable to peruse .DBG file msjava.dbg ("") err:dbghelp:pe_load_dbg_file -Unable to peruse .DBG file vmhelper.dbg ("") No symbols found for is Undefined symbol * ebd * I have to force exit with :- Wine-dbg>Ctrl-C: stopping debuggee On both cases installation went through w/o complaint. Started IE6 Tools -> Internet Options -> Advanced Can't find "MS VM" there. Pls help. TIA B.R. Stephen Liu Send instant messages to your online friends http://uk.messenger.yahoo.com

...Thread ID=001d renamed using MS VC6 extension (name=="") err:seh:setup_exception_record stack overflow 948 bytes in thread 0019 eip b7688ddc esp 00240f7c stack 0x240000-0x241000-0x3b0000 ^CCtrl-C: stopping debuggee 0xb7806430: popl %ebp Wine-dbg>bt all 0xb783942e: jmp 0xb7839423...

..... fixme:console:SetConsoleCtrlHandler (0x406205b0,1) - no error checking or testing yet WineDbg starting on pid 0xa Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x00000000). In 32 bit mode. 0x00000000: addb %al,0x0(%eax) Wine-dbg> Ctrl-C Ctrl-C: stopping debuggee [wparish@localhost ie6]$ WineDbg terminated on pid 0xa [wparish@localhost ie6]$ cd .. [wparish@localhost wine-hdd]$ rm -rf ie6/ [wparish@localhost wine-hdd]$ ls /home/wparish/.wine/d dosdevices drive_c [wparish@localhost wine-hdd]$ ls /home/wparish/.wine/drive_c/ autoexec.bat Local Settings/ Pr...

...tests for the Vulkan adapter. wined3d: Implement alpha to coverage multisampling for the Vulkan adapter. wined3d: Implement vertex attribute divisors for the Vulkan adapter. wined3d: Move the swapchain fps counter to wined3d_cs_exec_present(). Jacek Caban (24): dbghelp: Use debuggee environment in search_unix_path. notepad: Use int for point size value. dmscript: Remove unused function. winegcc: Introduce --debug-file option for generating separated symbol files. configure: Allow specifying cross debug format. makedep: Support split debug for cros...

I would like to be able to trace execution into calls below the current function, or to follow execution as calls return. This is roughly the distinction between "step" and "next" in many debuggers. I would also like to be able to switch to a location further up the call stack than the location at which I enter the debugger, to see the context of the current operations. Are

...enumeration callbacks. dbghelp: Split elf_load_file into two functions (one for creating a file-map, another one for loading info out of a file-map). dbghelp: Use pread instead of read in elf_map_file. dbghelp: Extend elf_map_file so that it can also handle ELF maps directly from debuggee address space. dbghelp: For targets on Linux, report the VDSO system page as a known ELF module. Eryk Wieliczko (1): msvcrt: Implement _ftime64_s and _ftime32_s. Francois Gouget (2): shdocvw/tests: Fix compilation on systems that don't support nameless unions. winemenu...

...r references on function signature. dbghelp: module target: Better error handling when init fails and creates a dummy thread. winedbg: We no longer need to force for ELF modules in minidumps as we do it automatically now. winedbg: Forward the wShowWindow option from winedbg to the debuggee. dbghelp: Added helper to get the basename + extension from full filename. dbghelp: Rewrote module_is_elf_container_loaded so that it no longer dbghelp: Cleanups for module loading (lookups on module name and image name are two different things) dbghelp: Get rid of module_na...

...lock() to the front and remove the forward declaration. shlwapi: Update win32.api to fix the winapi_check warnings. wininet: Fix many wininet prototypes: the context is a DWORD_PTR now. wininet: Remove the occasional parameter name in the prototypes. winedbg: Detach from the debuggee before exiting. bcrypt: Add a skeleton bcrypt.h header and use it. winedbg: 'winedbg --auto' and 'winedbg --minidump' should detach when done so as to not mess up the crashed process exit code. server: Fix the crashed process exit code when the debugger exits witho...