> The only snag could be, does PE format allow a separate base address
> for each "segment", or are all segments fixed relative to each other,
> like the PT_LOAD in ET_DYN?
>
each segment is described as an offset to the module's base address, but
the offset are fixed in the PE format (as well
>> the hard part is to tell valgrind about information about modules it
>> doesn't know of:
>> - it doesn't know about the loading of the module (it's seen by vg as a
>> simple mmap)
>> - it doesn't know about the PE native debug information (whatever it is)
>>
>> the simplest approach would be to
Eric Pouech wrote:
> Dan Kegel a écrit :
>> ... I can run Picasa for Windows under Wine under Valgrind.
>> It seemed to find lots of little problems, but since there
>> were lots of numeric addresses without symbolic info in the
>> valgrind log, it wasn't directly useful to the Picasa developers.
On Jan 16, 2008 12:25 PM, Eric Pouech <[EMAIL PROTECTED]> wrote:
> the hard part is not about understanding the .pdb format
> our winedump already does it !!
> and dbghelp supports coff and .pdb debug information (less tested than
> stabs and dwarf2 of course)
That's good to hear. I must have bli
On Jan 16, 2008 12:25 PM, Eric Pouech <[EMAIL PROTECTED]> wrote:
> btw: the bug (11211) is rather strange. the crash occurs while loading
> dwarf information, not pdb. Does it occurs in every usage of winedbg ?
I'm not sure. It happens lots, not just on this app.
I haven't looked into it at all.
Dan Kegel a écrit :
> This script,
> http://kegel.com/wine/valgrind/valgrind-330-build.sh
> builds a copy of valgrind-3.3.0 with
> John Reiser's forward port of the Wine support patch.
> With that, I can run Picasa for Windows under Wine under Valgrind.
> It takes 40 seconds to start up on my 1.3GH
This script,
http://kegel.com/wine/valgrind/valgrind-330-build.sh
builds a copy of valgrind-3.3.0 with
John Reiser's forward port of the Wine support patch.
With that, I can run Picasa for Windows under Wine under Valgrind.
It takes 40 seconds to start up on my 1.3GHz Athlon 64,
which is right in l
