[reposted because I posted not from the subscribed address - Doh! Sorry if you see it twice in the end]
Using the RH9 RPM from the SF downloads area (wine-20040121-1rh9winehq.i686.rpm)
This is my first serious attempt at getting a non-working app working, so if I am giving insufficient, or the wrong kind of, info, or am asking on the wrong list, or have not found the blindingly-obvious-to-everyone-but-me FAQ covering something then please point me at the right things.
At my company, we have just purchased a spangly new Alcatel telephone exchange, and despite the exchange running Linux apparently (I am going to start work on obtaining the source next week ...), they have only a Windows client for managing this exchange. Thus Wine ....
The management software (binary called pm5.exe) installed fairly easily and gets a long way in on execution but then stops making progress. It consumes pretty much all the CPU and when run with debug messages printed I get the following:
fixme:ole:CoRegisterMessageFilter stub warn:heap:HEAP_ValidateInUseArena Heap 40220000: invalid in-use arena magic for 402576a0 warn:ole:create_marshalled_proxy Could not open named pipe to broker \.\pipe{46A9F31C-E868-11D4-8BC9-000102A831DC}, le is 2 [last message repeated indefinitely]
There are two earlier instances of the first message, so I don't think that is the fundamental problem, but that is the first and only HEAP message, and the last message gets repeated endlessly. (full logs available on request).
It also looks for, and doesn't find, ADVAPI32.dll.
I am not a Windows person at all, so have no idea if the above dll is one that I should expect to find somewhere, or likely to be from the app itself. As for the pipe thing, I couldn't tell whether it couldn't connect because it couldn't make a pipe, or because it could but there was nothing at the end of it. (I am assuming the 'broker' is at the other end of the pipe.)
Can anyone advance my state here?
Cheers,
Peter
The management software (binary called pm5.exe) installed fairly easily and gets a long way in on execution but then stops making progress. It consumes pretty much all the CPU and when run with debug messages printed I get the following:
fixme:ole:CoRegisterMessageFilter stub
Should be harmless.
warn:heap:HEAP_ValidateInUseArena Heap 40220000: invalid in-use arena magic for 402576a0
Worrying, but your program hasn't crashed so shouldn't be a problem.
warn:ole:create_marshalled_proxy Could not open named pipe to broker \.\pipe{46A9F31C-E868-11D4-8BC9-000102A831DC}, le is 2 [last message repeated indefinitely]
Probably the real cause. That pipe path isn't a standard Windows one. Is there some server software you should run?
There are two earlier instances of the first message, so I don't think that is the fundamental problem, but that is the first and only HEAP message, and the last message gets repeated endlessly. (full logs available on request).
It also looks for, and doesn't find, ADVAPI32.dll.
You have run with warn+all right? That means it is a bit verbose when loading DLLs. If wine really can't find a DLL it will let you know in an err: message.
I am not a Windows person at all, so have no idea if the above dll is one that I should expect to find somewhere, or likely to be from the app itself. As for the pipe thing, I couldn't tell whether it couldn't connect because it couldn't make a pipe, or because it could but there was nothing at the end of it. (I am assuming the 'broker' is at the other end of the pipe.)
Yes, try looking for something that needs to be at the other end of the pipe (most likely another executable).
Rob
"Robert Shearman" R.J.Shearman@warwick.ac.uk writes:
warn:heap:HEAP_ValidateInUseArena Heap 40220000: invalid in-use arena magic for 402576a0
Worrying, but your program hasn't crashed so shouldn't be a problem.
Well the thing that I *think* should be on the other end of the pipe crashes with a similar message:
warn:heap:HEAP_ValidateInUseArena Heap 40220000: invalid in-use arena magic for 40257990
The only other occurrance of that address (40257990) for the putative server process is:
trace:heap:RtlAllocateHeap (0x40220000,00000002,00000108): returning 40257990
As I am a novice at this wine debugging malarchy, I don't know what an arena is, much less its magic, so I have no idea how I might determine if the application is currupting it or there is a wine bug. (acknowledging of course that wine has *no* bugs ... :-P)
warn:ole:create_marshalled_proxy Could not open named pipe to broker \.\pipe{46A9F31C-E868-11D4-8BC9-000102A831DC}, le is 2 [last message repeated indefinitely]
Probably the real cause. That pipe path isn't a standard Windows one. Is there some server software you should run?
I think I have found a server binary (see above), but it crashes so I am not sure. Can I use nm or something similar to look for calls to whatever functions are likely to create the pipe, so as to at least make sure I am dealing with the correct binary. (we have no instructions yet...)
It also looks for, and doesn't find, ADVAPI32.dll.
You have run with warn+all right?
Yes.
That means it is a bit verbose when loading DLLs. If wine really can't find a DLL it will let you know in an err: message.
I get no err messages.
Is it reasonably safe therefore to assume that it would *like* this dll, but doesn't *need* it.
"Peter" == Peter Riocreux par+wine_devel@silistix.com writes:
Peter> "Robert Shearman" R.J.Shearman@warwick.ac.uk writes: >> > warn:heap:HEAP_ValidateInUseArena Heap 40220000: invalid in-use > >> arena magic for 402576a0 >> >> Worrying, but your program hasn't crashed so shouldn't be a problem.
Peter> Well the thing that I *think* should be on the other end of the Peter> pipe crashes with a similar message:
Peter> warn:heap:HEAP_ValidateInUseArena Heap 40220000: invalid in-use Peter> arena magic for 40257990
Run with --debugmsg +heap , eventaully with --debugmsg +relay,+heap. That way, wine checks the heap on every heap access and stops and prints a debug when the heap is strange.
However the logs tend to get long and the execution speed to crawl...
Hope this helps
Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de writes:
"Peter" == Peter Riocreux par+wine_devel@silistix.com writes:
Peter> "Robert Shearman" <R.J.Shearman@warwick.ac.uk> writes: >> > warn:heap:HEAP_ValidateInUseArena Heap 40220000: invalid in-use > >> arena magic for 402576a0 >> >> Worrying, but your program hasn't crashed so shouldn't be a problem. Peter> Well the thing that I *think* should be on the other end of the Peter> pipe crashes with a similar message: Peter> warn:heap:HEAP_ValidateInUseArena Heap 40220000: invalid in-use Peter> arena magic for 40257990Run with --debugmsg +heap , eventaully with --debugmsg +relay,+heap. That way, wine checks the heap on every heap access and stops and prints a debug when the heap is strange.
However the logs tend to get long and the execution speed to crawl...
That is how I got the info from my last post in this threadlet. I am not clear whetherthtis means that it is wine internal corruption as there is no complaint on the other time this address is recorded, but this time it is bad.
Peter
Peter Riocreux wrote:
fixme:ole:CoRegisterMessageFilter stub warn:heap:HEAP_ValidateInUseArena Heap 40220000: invalid in-use arena magic for 402576a0 warn:ole:create_marshalled_proxy Could not open named pipe to broker \.\pipe{46A9F31C-E868-11D4-8BC9-000102A831DC}, le is 2 [last message repeated indefinitely]
Hi Peter,
This is a problem with OLE32, not with named pipes. The interprocess marshalling code in Wine's OLE32 implementation is not yet complete...
Mike
Mike McCormack mike@codeweavers.com writes:
Peter Riocreux wrote:
fixme:ole:CoRegisterMessageFilter stub warn:heap:HEAP_ValidateInUseArena Heap 40220000: invalid in-use arena magic for 402576a0 warn:ole:create_marshalled_proxy Could not open named pipe to broker \.\pipe{46A9F31C-E868-11D4-8BC9-000102A831DC}, le is 2 [last message repeated indefinitely]
This is a problem with OLE32, not with named pipes. The interprocess marshalling code in Wine's OLE32 implementation is not yet complete...
Thanks for the diagnosis. Is it something that someone is working on, but just not finished, or is it something that nobody is really attacking at the moment? The status system on the website suggests it is 60% complete, and it was last mentioned in WWN #117, but that isn't necessarily a guide to activity on it.
Is it something that someone not steeped in the magic of Wine/Windows might be able to hack on? If it is practical for me to do so in my limited spare time, I would happily write code in exchange for guidance...
Peter
On Wed, 28 Jan 2004 13:04:44 +0000, Peter Riocreux wrote:
warn:ole:create_marshalled_proxy Could not open named pipe to broker \.\pipe{46A9F31C-E868-11D4-8BC9-000102A831DC}, le is 2 [last message repeated indefinitely]
Hi,
Install native DCOM (see #winehq channel faq), then run with
WINEDLLOVERRIDES="ole32,oleaut32,rpcrt4=n" wine whatever.exe
See if that helps.
thanks -mike
-
Mike Hearn -
Mike McCormack -
Peter Riocreux -
Robert Shearman -
Uwe Bonnes