Re: Wine under -current. patches.. comments?

[Juergen Lock]

In article [EMAIL PROTECTED] you write:
 The latest port of wine references PR 14652
 for patches to make -current work.
 some of these ptches are however in areas I don't understand.
 In particular signals, register contexts, etc.

This refers to validity of segment registers fs/gs in sigcontext.
Under -stable both of them are unused and signal handlers have to
read the registers directly. Under -current fs was valid and gs
still unused until I changed it recently, now they are both valid.
This was done a couple weeks before 3.3-RELEASE, so I didn't have
time to change -stable as well. I planned to do it immediately
afterwards, but Marcel's 128-signal change came in, and I decided
to wait for -current to stablize first. I guess it's time for me to
make the changes. A word of warning, after the changes wine should
be source compatible between -stable and -current, binary compiled
on -stable should still work on -current,

This is good news...

 but not vice versa.

 And thats to be expected of course.

There's another patch regarding SIGTRAP in the PR. I recall there
were some discussions about it, but I don't know what's the final
resolution (if there was one). Maybe Marcel and Bruce know better.

 The last mail i received on the subject if i remember right was
Bruce's with the suggestion to use the state of the trace bit on
entry to syscall() (not on exit as my first version did), which i
then tested and which worked, and this is the version now in the
port (files/patch-3.3-sys-sigtrap).

 Regards,
-- 
Juergen Lock [EMAIL PROTECTED]
(remove dot foo from address to reply)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Wine under -current. patches.. comments?

[Luoqi Chen]

 The latest port of wine references PR 14652
 for patches to make -current work.
 some of these ptches are however in areas I don't understand.
 In particular signals, register contexts, etc.

This refers to validity of segment registers fs/gs in sigcontext.
Under -stable both of them are unused and signal handlers have to
read the registers directly. Under -current fs was valid and gs
still unused until I changed it recently, now they are both valid.
This was done a couple weeks before 3.3-RELEASE, so I didn't have
time to change -stable as well. I planned to do it immediately
afterwards, but Marcel's 128-signal change came in, and I decided
to wait for -current to stablize first. I guess it's time for me to
make the changes. A word of warning, after the changes wine should
be source compatible between -stable and -current, binary compiled
on -stable should still work on -current, but not vice versa.

There's another patch regarding SIGTRAP in the PR. I recall there
were some discussions about it, but I don't know what's the final
resolution (if there was one). Maybe Marcel and Bruce know better.

 There is reference to a patch of luoqi's as well as other comments.

This is the ldt sharing patch I had a while ago. It's still in my local
tree, but I haven't updated the patch on my web page for a long time.
I wanted to commit this patch, but I haven't found any one with enough
time and interest to review it. Julian, would you? I can send you the
latest diff.

 Some of the patches are simply to newer code back to 3.3 but there are
 obviously problems with -current as well.
 
 Is there anyone with their fingers in that stuff that has a patchset for
 -current?
 
If I could get the ldt sharing stuff committed, the patchset would be
a lot more manageable :-)

 Julian
 

-lq


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message