Re: Help with winedbg

2004-05-30 Thread Eric Pouech
Shachar Shemesh a écrit : Eric Pouech wrote: Apparently, there is a problem even without gdb at all. Attached is the output for running "winedbg program", with no arguments at all. The system is a RedHat 9 with kernel 2.4.20-31.9, and the latest glibc available from redhat for it. Wine is CVS ti

Re: Help with winedbg

2004-05-30 Thread Shachar Shemesh
Eric Pouech wrote: Apparently, there is a problem even without gdb at all. Attached is the output for running "winedbg program", with no arguments at all. The system is a RedHat 9 with kernel 2.4.20-31.9, and the latest glibc available from redhat for it. Wine is CVS tip for today.

Re: Help with winedbg

2004-05-30 Thread Eric Pouech
Apparently, there is a problem even without gdb at all. Attached is the output for running "winedbg program", with no arguments at all. The system is a RedHat 9 with kernel 2.4.20-31.9, and the latest glibc available from redhat for it. Wine is CVS tip for today. Shachar err:winecon

Re: Help with winedbg

2004-05-30 Thread Shachar Shemesh
Eric Pouech wrote: (the latest wine misses the debug information for the .spec.c files, and that's were main is... could you print the name of the file and the exact error message) See below. Don't have them at the moment. Is there any workaround? What do I do if there is no debug symbols for t

Re: Help with winedbg

2004-05-26 Thread Eric Pouech
(the latest wine misses the debug information for the .spec.c files, and that's were main is... could you print the name of the file and the exact error message) See below. Don't have them at the moment. Is there any workaround? What do I do if there is no debug symbols for that part at all. Wh

Re: Help with winedbg

2004-05-26 Thread Shachar Shemesh
Eric Pouech wrote: 1. Use Visual Studio's remote debugging never tried it, cannot help you here Oh, it's great when it works. Obviously, no ELF or Winelib symbols, but you are essentially using the standard visual studio debugger on a program running in Wine. I used that to try and understand wh

Re: Help with winedbg

2004-05-26 Thread Eric Pouech
1. Use Visual Studio's remote debugging never tried it, cannot help you here 2. Use winedbg as a gdb backend for ddd Option 1 fails miserably. I suspect the project is just too complex for Visual Studio to handle over the wire. When I try to do that, the Visual Studio front end (the one running o

Help with winedbg

2004-05-26 Thread Shachar Shemesh
Hi, I'm trying to get a Visual C compiled program to run on Wine. I have the sources and full debug info for the PE part of the program. Obviously, however, it was not compiled on the same machine on which it is running. To make things even more interesting, I would rather use some GUI frontend