Francois Gouget writes:
> On Wed, 1 Nov 2000, Uwe Bonnes wrote:
>
> > Ulrich Weigand writes:
> > > Hello,
> > >
> > > To do so, simply replace the debugger/msc.c file with the
> > > attached new version. Please give feedback whether it
> > > works for you or not ...
> > >
> > >
> > Hallo,
> >
> > I am still trying to get a sensible backtrace for the MFC programm
> > so I can perhaps find out where the bad arguments to CreateWindowEx
> > com from.
>
> You want function names for the MFC functions, right?
Yeah, I'm greedy :-)
> Maybe the problem is that the MFC dll exports all its functions by
> ordinal. At least the one I have here. I don't know if debug information
> can compensate that (I guess it should).
>
Well, some dll exports get resolved to something, and display source code
line pointers.
Other dll exports don't get resolved...
How to we find out what can be expected from the mfc42.dll/mfc42.pdb
combo?
I tried different debuggers on the said programm with vmware/winxx,
but I was not able to set a breakpoint at a similar point like in wine
to compare backtraces.
> Just a random thought.
>
And even those stackframes that get resolved seem like they don't get
resolved right. Looking at the mfc source, I don't think these places
called the next frame or where called by the previous...
Bye
Uwe Bonnes [EMAIL PROTECTED]
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
