On Thursday 27 July 2006 23:53, Julian Elischer wrote:
> Tijl Coosemans wrote:
> > On Thursday 27 July 2006 17:21, John Baldwin wrote:
> > > The kernel should preserve %fs across syscalls, traps, and faults.
> > > Can you point to a specific case where %fs is not preserved? It
> > > sounds like %f
Tijl Coosemans wrote:
On Thursday 27 July 2006 17:21, John Baldwin wrote:
On Monday 24 July 2006 21:58, Tijl Coosemans wrote:
However, Wine/Windows uses %fs for TLS and it appears that the
FreeBSD kernel doesn't preserve it. It always ends up pointing to
GUDATA_SEL.
The kernel s
On Thursday 27 July 2006 17:21, John Baldwin wrote:
> On Monday 24 July 2006 21:58, Tijl Coosemans wrote:
> > However, Wine/Windows uses %fs for TLS and it appears that the
> > FreeBSD kernel doesn't preserve it. It always ends up pointing to
> > GUDATA_SEL.
>
> The kernel should preserve %fs acros
On Monday 24 July 2006 21:58, Tijl Coosemans wrote:
> On Monday 24 July 2006 18:49, Daniel Eischen wrote:
> > On Mon, 24 Jul 2006, Tijl Coosemans wrote:
> > > On Monday 24 July 2006 17:39, Daniel Eischen wrote:
> > >> On Mon, 24 Jul 2006, Tijl Coosemans wrote:
> > >>> I've attached two patches that
On Monday 24 July 2006 18:49, Daniel Eischen wrote:
> On Mon, 24 Jul 2006, Tijl Coosemans wrote:
> > On Monday 24 July 2006 17:39, Daniel Eischen wrote:
> >> On Mon, 24 Jul 2006, Tijl Coosemans wrote:
> >>> I've attached two patches that accomplish this, but this seems to
> >>> trigger other proble
Gerald Pfeifer wrote:
On Mon, 24 Jul 2006, Daniel Eischen wrote:
See my response to this in a previous reply to this thread. libthr
and libpthread use LDT's for TLS. WINE is stomping on them because
it doesn't properly create LDTs. This is not a problem with either
of the thread libraries
On Mon, 24 Jul 2006, Tijl Coosemans wrote:
On Monday 24 July 2006 17:39, Daniel Eischen wrote:
On Mon, 24 Jul 2006, Tijl Coosemans wrote:
I've attached two patches that accomplish this, but this seems to
trigger other problems, so use at your own risk. If you want to try
them, place them in th
On Monday 24 July 2006 17:39, Daniel Eischen wrote:
> On Mon, 24 Jul 2006, Tijl Coosemans wrote:
> > I've attached two patches that accomplish this, but this seems to
> > trigger other problems, so use at your own risk. If you want to try
> > them, place them in the port's files/ directory and add
On Mon, 24 Jul 2006, Daniel Eischen wrote:
> See my response to this in a previous reply to this thread. libthr
> and libpthread use LDT's for TLS. WINE is stomping on them because
> it doesn't properly create LDTs. This is not a problem with either
> of the thread libraries and this issue has b
On Mon, 24 Jul 2006, Tijl Coosemans wrote:
On Saturday 22 July 2006 19:14, Michael Nottebrock wrote:
WINE does have certain requirements regarding memory allocation. In
particular it (or Windows, rather) really wants a few memory ranges
for itself:
(from wine-0.9.17/loader/preloader.c):
* 0
On Saturday 22 July 2006 19:14, Michael Nottebrock wrote:
> WINE does have certain requirements regarding memory allocation. In
> particular it (or Windows, rather) really wants a few memory ranges
> for itself:
>
> (from wine-0.9.17/loader/preloader.c):
>
> * 0x - 0x0011 the DOS are
On Sun, 23 Jul 2006, Michael Nottebrock wrote:
On Sunday, 23. July 2006 01:15, Daniel Eischen wrote:
On Sat, 22 Jul 2006, Michael Nottebrock wrote:
On Saturday, 22. July 2006 21:20, Kip Macy wrote:
I think it is because WINE stomps on or TLS. Nothing we can
do about that except patch wine
On Sunday, 23. July 2006 01:15, Daniel Eischen wrote:
> On Sat, 22 Jul 2006, Michael Nottebrock wrote:
> > On Saturday, 22. July 2006 21:20, Kip Macy wrote:
> I think it is because WINE stomps on or TLS. Nothing we can
> do about that except patch wine so it doesn't. Look at the
> console messag
On Sunday, 23. July 2006 00:59, Kip Macy wrote:
> Thanks. That is a useful data point but David Xu has done a lot of
> work on libthr that has probably not been MFC'd back to 5.x. When I
> get the chance I'll try building KDE on my desktop which runs a
> derivative of -CURRENT.
At least on FreeBSD
On Sunday 23 July 2006 11:18, Divacky Roman wrote:
> On Sat, Jul 22, 2006 at 07:15:35PM -0400, Daniel Eischen wrote:
> > I think it is because WINE stomps on or TLS. Nothing we can
> > do about that except patch wine so it doesn't. Look at the
> > console messages for:
> >
> > Warning: pid XXX
On Sunday 23 July 2006 11:18, Divacky Roman wrote:
> On Sat, Jul 22, 2006 at 07:15:35PM -0400, Daniel Eischen wrote:
> > I think it is because WINE stomps on or TLS. Nothing we can
> > do about that except patch wine so it doesn't. Look at the
> > console messages for:
> >
> > Warning: pid XXX
On Sat, Jul 22, 2006 at 07:15:35PM -0400, Daniel Eischen wrote:
> On Sat, 22 Jul 2006, Michael Nottebrock wrote:
>
> >On Saturday, 22. July 2006 21:20, Kip Macy wrote:
> >>Thanks for your input.
> >>
> >>The relative merits of the different threading libraries is currently
> >>under discussion. Co
On Sat, 22 Jul 2006, Michael Nottebrock wrote:
On Saturday, 22. July 2006 21:20, Kip Macy wrote:
Thanks for your input.
The relative merits of the different threading libraries is currently
under discussion. Could you also try it with libthr (it may not work
at all), I'd like to hear what happ
Thanks. That is a useful data point but David Xu has done a lot of
work on libthr that has probably not been MFC'd back to 5.x. When I
get the chance I'll try building KDE on my desktop which runs a
derivative of -CURRENT. It may well be a general kernel bug, as I
recall seeing the same error run
On Saturday, 22. July 2006 21:20, Kip Macy wrote:
> Thanks for your input.
>
> The relative merits of the different threading libraries is currently
> under discussion. Could you also try it with libthr (it may not work
> at all), I'd like to hear what happens. Thanks.
WINE crashes in roughly the
Thanks for your input.
The relative merits of the different threading libraries is currently
under discussion. Could you also try it with libthr (it may not work
at all), I'd like to hear what happens. Thanks.
-Kip
On 7/22/06, Michael Nottebrock <[EMAIL PROTECTED]> wrote:
Dear -hackers and -
Dear -hackers and -emulation readers,
I would like to call your attention to a few long-standing problems that have
so far prevented WINE from living up to its capabilities on FreeBSD.
I am afraid that I still don't fully grasp the scope of the problem, nor do I
have a clear idea of what the so
22 matches
Mail list logo
