Shachar Shemesh wrote:
Ok, the above patch solves the problem for me. Does that mean we still
have some stack thrashing somewhere? Could it not be that the "-O2"
compilation option did the gdb warning?
Is this something valgrind can help with?
Shachar
Hi Eric,
Is there any reason not to
Eric Pouech wrote:
Shachar Shemesh a écrit :
What do you mean by "I don't need to use the S: directory"?
I thought you needed the S: dir for the PDB reading (in fact, you seem
to, rightfully, only need it for source files)
Yes. Actually, in the real program, the PDBs are not in the same
director
Shachar Shemesh a écrit :
What do you mean by "I don't need to use the S: directory"?
I thought you needed the S: dir for the PDB reading (in fact, you seem
to, rightfully, only need it for source files)
at least this works here... what's strange anyway in your case is that
it sometimes crash, a
On Sat, 2004-06-12 at 20:34 +0200, Rein Klazes wrote:
> BTW. I thought Crossover Office supports this application?
It does (well, not the NL version specifically ...) so I checked and the
CrossOver version of FindClose is the same as the WineHQ version. I seem
to recall some talk of double closing
What is a minidump? I saw them mentioned in the todo list but there weren't
many details.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/minidump_files.asp
Eric Pouech wrote:
Sample session of showdebug/semidebug$ WINEDEBUG=+dbghelp winedbg
showdebug.exe
Since there is lots of cruft there, I ran it once working and once
not, and am only pasting the diff between the two here. Those marked
with ">" are the lines when things are working (scroll to the
On Sat, 12 Jun 2004 19:13:05 +0200, Eric Pouech wrote:
> well, in that case the mini-dumps are the way to go (even if they don't
> have the pre-defined semantics for system wide thread information, but
> they do have what you need). This will embed more details that what
> you've done (OS versio
Mike Hearn a écrit :
On Fri, 2004-06-11 at 20:55 +0200, Eric Pouech wrote:
I'm not sure I understand the purpose of the --backtrace-all.
When a user says "I pressed this button and the app hung" it's
convenient to have *somewhere* to start from - this is another attack
vector.
well, in that case t
Sample session of showdebug/semidebug$ WINEDEBUG=+dbghelp winedbg
showdebug.exe
Since there is lots of cruft there, I ran it once working and once not,
and am only pasting the diff between the two here. Those marked with ">"
are the lines when things are working (scroll to the end to verify). Th
On Fri, 04 Jun 2004 15:34:41 +0200, you wrote:
> > If simply returning an error doesn't work, you need to improve the
> > stub to provide enough functionality for the app to be happy.
> well, the problem is that I'm not a programmer and I don't know in which
> way I should improve the stub. So I t
Lionel Ulmer wrote:
I have no idea if it's correct
though (as I do not know if what GetModuleHandle returns is really the same
thing as what SetWindowsHookEx expects as an HINSTANCE input).
Yes, it is. It's just used to grab the procedure address to call when
the hook is activated.
Index: dlls
Raul Dias wrote:
Hi,
I have problems with wine serial code since 2000/2001.
I think this might be related to your problem.
In my situation, I have a bunch of stores that runs linux.
Their sales sistem is remote application that can be run thru
ssh/telnet/...
Unfortunally they are required to use ex
Eric Pouech wrote:
Izak Burger a écrit :
Hello,
Perhaps I should appologise, I have been lurking on the list way too
long and this message just passed by while I was messing arround with
the next project, which gladly does not involve serial comms and wine :-)
does this fix it ?
A+
This works fo
13 matches
Mail list logo
