[Bug 13275] Remedy User WIndow crashes following login to ar server

Thu Apr 16 12:52:15 CDT 2009

http://bugs.winehq.org/show_bug.cgi?id=13275

--- Comment #10 from Michael H. Warfield <mhw at wittsend.com>  2009-04-16 12:52:15 ---
Now tested under 1.1.19.  Same problems.  I built rpm's for Fedora 10 with
1.1.19 and reran the test with Gecko installed.  Problem reported in the log is
this with Gecko in place:

wine: Call from 0x7bc48320 to unimplemented function
nspr4.dll.PR_GetPhysicalMemorySize, aborting
wine: Unimplemented function nspr4.dll.PR_GetPhysicalMemorySize called at
address 0x7bc48320 (thread 0009), starting debugger...
Unhandled exception: unimplemented function nspr4.dll.PR_GetPhysicalMemorySize
called in 32-bit code (0x7bc48320).
Register dump:

:

Backtrace:
=>0 0x7bc48320 stub_entry_point+0x50(dll="nspr4.dll",
name="PR_GetPhysicalMemorySize", ret_addr=0x2339905)
[/usr/src/debug/wine-1.1.19/dlls/ntdll/loader.c:189] in ntdll (0x0032d818)
  1 0x02e006ea (0x0032d874)
  2 0x02339d5d in xul (+0x889d5d) (0x0032d924)
  3 0x022e6807 in xul (+0x836807) (0x0032d944)
  4 0x025e183a in xul (+0xb3183a) (0x0032d9b4)

Ok...  Sounds like we need a function implemented there.

Without Gecko and going for the search function, it still bombs with an
unhandled page fault in aruser called from mfc71:

wine: Unhandled page fault on read access to 0x00000588 at address 0x612cdc
(thread 0009), starting debugger...
Unhandled exception: page fault on read access to 0x00000588 in 32-bit code
(0x00612cdc).
Register dump:
 CS:0073 SS:007b DS:007b ES:007b FS:0033 GS:003b
 EIP:00612cdc ESP:0032b3d8 EBP:0032b460 EFLAGS:00010212(   - 00      - RIA1)
 EAX:0032b4bc EBX:00000111 ECX:0032b510 EDX:000002cc
 ESI:00774e60 EDI:00000001

:

Backtrace:
=>0 0x00612cdc in aruser (+0x212cdc) (0x0032b460)
  1 0x00612f18 in aruser (+0x212f18) (0x0032b4c8)
  2 0x00612e5c in aruser (+0x212e5c) (0x0032b4dc)
  3 0x00612e1e in aruser (+0x212e1e) (0x0032b4ec)
  4 0x004dfb53 in aruser (+0xdfb53) (0x0032b658)
  5 0x004df9c4 in aruser (+0xdf9c4) (0x0032b6a8)
  6 0x00472595 in aruser (+0x72595) (0x0032b9dc)
  7 0x0040c5e7 in aruser (+0xc5e7) (0x0032bdac)
  8 0x0040ca97 in aruser (+0xca97) (0x0032bdfc)
  9 0x0041655e in aruser (+0x1655e) (0x0032c200)
  10 0x004fea46 in aruser (+0xfea46) (0x0032c294)
  11 0x0050c355 in aruser (+0x10c355) (0x0032c2a8)
  12 0x0050c282 in aruser (+0x10c282) (0x0032c2b4)
  13 0x7c1746cc in mfc71 (+0x346cc) (0x0032c2c4)
  14 0x7c171915 in mfc71 (+0x31915) (0x0032c2f4)
  15 0x7c14db36 in mfc71 (+0xdb36) (0x0032c318)
  16 0x7c175cd8 in mfc71 (+0x35cd8) (0x0032c368)

This sounds bad and sounds like it's different from the first problem.

Full logs will be attached.

I've now pulled down the git repository and should be able to generate patches
and test.  What information can I gather and how can I help?

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.