y the INT2F handler and by the
interrupt routine.
2. Next, I send a patch fixing the bugs.
Is that right?
Petr Tesarik
On 04/07/06 at 14:53:34 (+0200), Alexandre Julliard wrote:
> Petr Tesarik <[EMAIL PROTECTED]> writes:
>
> > Hi everyone,
> >
> > has this patch been re
tches applied (including one to
the Linux kernel, which was accepted in 2.6.15), I can now run Kindler
Literaturlexikon with Wine. And I'd enjoy adding that application to
the appdb.
Petr
Dne 03/31/06 v 14:29:38 (+0200), Petr Tesarik napsal(a):
> Hi,
>
> while I was trying to make Kindl
different platform, as it is very likely that it can be made
to work too, but I won't send patches which I can't test.
To the wine-devel list: Why was the patch rejected, anyway?
Petr Tesarik
On 03/29/06 at 09:35:04 (-0800), Dan Kegel wrote:
> On 3/29/06, Petr Tesarik <[EMAIL PROTECTE
Dne 03/27/06 v 17:19:47 (+0200), Petr Tesarik napsal(a):
> Dne 03/27/06 v 08:03:58 (-0700), Vitaliy Margolen napsal(a):
> > Monday, March 27, 2006, 12:51:03 AM, Petr Tesarik wrote:
> > > [skip]
> >
> > > * Look at ContextFlags to see which registers are
On 06/03/27 at 18:19:44 (+0200), Alexandre Julliard wrote:
> Petr Tesarik <[EMAIL PROTECTED]> writes:
>
> > That means that Windows XP creates a new thread in the given process
> > and breaks it at DbgBreak().
> >
> > Does this mean that we may avoid sending
088C, Thread ID: 080C
Child process exited
That means that Windows XP creates a new thread in the given process
and breaks it at DbgBreak().
Does this mean that we may avoid sending SIGTRAP altogether?
Petr Tesarik
--- End Message ---
ess, there will be more
such platforms. AFAIK SIGTRAP is only sent internally by wineserver
for DebugBreakProcess(). I'll have a look at it.
Petr Tesarik
Dne 03/27/06 v 08:03:58 (-0700), Vitaliy Margolen napsal(a):
> Monday, March 27, 2006, 12:51:03 AM, Petr Tesarik wrote:
>
> > Hi,
>
> > this patch fixes a bug in get_thread_context(). Currently, this
> > routine assumes that all registers except debug registers are sav
Dne 03/27/06 v 16:49:13 (+0200), Alexandre Julliard napsal(a):
> Petr Tesarik <[EMAIL PROTECTED]> writes:
>
> > In my opinion, the solution is reasonable because if any application
> > is really interested in the DR6 register (i.e. it is a debugger), it
> > will
Dne 03/27/06 v 16:05:15 (+0200), Alexandre Julliard napsal(a):
> Petr Tesarik <[EMAIL PROTECTED]> writes:
>
> > No, Windows need not do things like that, because the Windows kernel
> > knows very well, whether it got INT1 or INT3... Some UNIX kernels do
> > not giv
Dne 03/27/06 v 16:05:15 (+0200), Alexandre Julliard napsal(a):
> Petr Tesarik <[EMAIL PROTECTED]> writes:
>
> > No, Windows need not do things like that, because the Windows kernel
> > knows very well, whether it got INT1 or INT3... Some UNIX kernels do
> > not giv
Hi,
I've just submitted a patch that handles the FPU state in signal
handlers. However, the FPU_sig() macro is only defined for Linux, so
other architectures won't benefit from that patch.
I doubt that i387 FPU state is left untouched by the kernel on other
architectures, but I have no access to
Dne 02/13/06 v 18:49:46 (+0900), Mike McCormack napsal(a):
>=20
> Petr Tesarik wrote:
>=20
> ># Keep the patch small and the point of the change clear.
> ># Submit one fix or group of related changes per patch.
> >
> >Well, OK, I could possibly break the patch in
resource files. No C/C++ comments at all.
# Read the diff and make sure it contains only what you want in it.
Done.
Thanks for any clue,
Petr Tesarik
14 matches
Mail list logo
