Hi,
I've never used DDD myself, but you shouldn't need winedbg as an intermediary unless you want to read Windows debugging symbols. You should be able to just attach DDD to the Linux Wine process or start wine from DDD.
Be aware that Wine uses SIGUSR1 to implement certain Win32 functions like SuspendThread or system APCs. If your debugged process receives a SIGUSR1 signal this is generally not an issue. I recommend to tell DDD to ignore it.
Am 08.10.2019 um 18:54 schrieb Thales thaleslv@yahoo.com:
Hello,
I'm John Alway. I program in C and C++, among other languages. This is my first message to the list. I've been playing around with the Wine repository for a while and have delved into some of the Bugzilla errors posted on "bugs.winehq.org." In the process of doing this, I've been using the "winedbg" executable with the "--gdb" switch set. That works fine for debugging, but lately I've been trying to employ the graphical application DDD, Data Display Debugger, with the winedbg executable. I've followed the instructions at this link:
https://wiki.winehq.org/Wine_Developer%27s_Guide/Debugging_Wine#DDD
When I do winedbg comes to life, but then fails. The error reads "Err: winedbg extract_packets Dropping packets: I was too slow to respond" . I do see this error on occasion even when not using DDD, and I can still work, so I don't know if that's the reason it stops.
Does anyone have any insights into using this, or is there a better way altogether? I like a visual display where I can see several elements at once.
Thanks for any help!
Regards, ...John Alway