> On Wed, 11 May 2005 23:01:17 +1200, Adrian Harvey wrote:
> > Well, I got some output at least! Never used strace before, but it
> > looks kinda like a +relay trace for the kernel :-)
>
> Yep, that's exactly what it is :)
>
> > I also happened to be tailing the syslog (I was looking at somet
On Wed, 11 May 2005 23:01:17 +1200, Adrian Harvey wrote:
> Well, I got some output at least! Never used strace before, but it
> looks kinda like a +relay trace for the kernel :-)
Yep, that's exactly what it is :)
> I also happened to be tailing the syslog (I was looking at something
> complete
> On Mon, 09 May 2005 21:44:58 +1200, Adrian Harvey wrote:
> > If I try to GDB wine I get all sorts of ugly errors
>
> Try an strace in "follow forks mode". Does that help?
>
> thanks -mike
Ok, here goes:
$ WINEDEBUG=+relay strace -f wine
execve("/usr/local/bin/wine", ["wine"], [/* 34 vars */
On Mon, 09 May 2005 21:44:58 +1200, Adrian Harvey wrote:
> If I try to GDB wine I get all sorts of ugly errors
Try an strace in "follow forks mode". Does that help?
thanks -mike
Adrian Harvey wrote:
This GDB was configured as "x86_64-redhat-linux-gnu"...Using host
libthread_db library "/lib64/tls/libthread_db.so.1".
I may be getting hung up on 64-bits for nothing, but is it possible for
a 64-bit debugger (using 64-bit libs) to properly debug a 32-bit binary?
Dustin
On Sun, 2005-05-08 at 17:41 -0400, Vincent BÃron wrote:
[snip]
> Relay shouldn't segfault, and it's still supported. I guess Adrian (if
> nobody else can reproduce) will need to add further traces or go through
> it with a debugger.
>
> Vincent
If I try to GDB wine I get all sorts of ugly errors
On Sun, 2005-05-08 at 15:53 -0500, Dustin Navea wrote:
> Adrian Harvey wrote:
> > Thanks, Dustin, that sorts the riched problem. Any ideas as to why the
> > relay trace segfaults though? That was the bit I thought was
> > interesting... I have now found it will segfault even if wine is not
> > g
Le dim 08/05/2005 à 16:53, Dustin Navea a écrit :
> Adrian Harvey wrote:
> > Thanks, Dustin, that sorts the riched problem. Any ideas as to why the
> > relay trace segfaults though? That was the bit I thought was
> > interesting... I have now found it will segfault even if wine is not
> > given
Adrian Harvey wrote:
Thanks, Dustin, that sorts the riched problem. Any ideas as to why the
relay trace segfaults though? That was the bit I thought was
interesting... I have now found it will segfault even if wine is not
given an executable, so it's happening very early on.
There are a couple
Thanks, Dustin, that sorts the riched problem. Any ideas as to why the
relay trace segfaults though? That was the bit I thought was
interesting... I have now found it will segfault even if wine is not
given an executable, so it's happening very early on.
Adrian
On Sun, 2005-05-08 at 04
This a known bug. head to http://bugs.winehq.org/show_bug.cgi?id=2924
for more info and a workaround..
We are waiting on the person that made this patch to post a fixed patch..
Alexandre.. This is generating a lot of bug reports, is there a chance
we could remove it for now, as it seems to have
The wine version of riched20 fails an assertion when starting
StreamboxVCR
$ wine .wine/drive_c/Program\
Files/StreamboxVcrSuite2/StreamBoxVCR1Beta31/vcr_31turbo.exe
fixme:ole:CoRegisterMessageFilter stub
fixme:ole:CoCreateInstance no classfactory created for CLSID {4955dd33-
b159-11d0-8fcf-00aa00
12 matches
Mail list logo
