444261 - WinDbg reports Firefox symbol file does not have correct symbols

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Brad Stiritz]

User-Agent:       Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; WOW64; GoogleT5; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.04506; Media Center PC 5.0)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0

I am trying to generate a FF stacktrace for an Adobe Flash 9 & Flash 10 beta 2-related hang. WinDbg says the PDB does not have full type information.

Reproducible: Always

Steps to Reproduce:
1. Run WinDbg
2. Launch FF using:
"C:\Program Files (x86)\Mozilla Firefox\firefox.exe" -safe-mode
.sympath SRV*c:\symbols*http://symbols.mozilla.org/firefox
.symfix+ c:\symbols
.reload /f
3.After FF hangs, execute this command in WinDbg:
!analyze -v -hang
Actual Results:  
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Your debugger is not using the correct symbols                 ***
***                                                                   ***
***    In order for this command to work properly, your symbol path   ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: kernel32!pNlsUserInfo                         ***
***                                                                   ***
*************************************************************************

Expected Results:  
stack trace for Firefox.exe

Comment 1

[(not currently active) Ted Mielczarek]

"Certain .pdb files (such as the public OS symbols) do not contain the required information."

The module mentioned there (kernel32.dll) is a Windows OS module. What would lead you to believe otherwise here? Can you just do a "kp" and get a backtrace? AFAIK the Firefox symbols are fine, they're the exact PDB files produced by the compiler, and I've used them for debugging without problems.

Comment 2

[Brad Stiritz]

Hi Ted,

Thanks for pointing out what should have been obvious to me (!) Sorry to not be very astute here. Let me please give a bit more context, and maybe you can please point me in the right direction..

I've been experiencing frequent FF 3.0 crashes since upgrading, versus few to none under FF 2.0. I searched the Mozilla bug database, and thought I had found a good match for what was happening - cf my posts in bug 423257.

In that bug comment thread, Mattias indicated to me that (a) my FF crashes weren't described by 423257; (b) my crashes are Flash-related; (c) you guys need a stack trace to pinpoint the problem; (d) I need to file a new bug.

So where I'm at currently is trying to accomplish (c), namely to get a stack trace. However, after all FF hangs to date, when I go to WinDbg, there's never any call stack info for FF.exe. So I filed this bug report in hopes that I can get help tracing the actual Flash problem, and then I'll file a bug report with that trace info..

Please understand, I'm trying to help out here, but I really was hoping to have to just do the absolute minimum thinking, as I have a lot of other responsibilities to worry about.

Sorry again about not realizing that WinDbg was complaining about Kernel32. I thought, incorrectly, that the FF PDB was missing symbol info b/c in the following "analyze" report, there appears to be very little useful call stack info for the Firefox.exe module--

Any suggestions / direction appreciated,
Thanks,
Brad

(FROM WINDBG)

FAULTING_IP: 
NPSWF32!native_ShockwaveFlash_TCallLabel+b0653
00000000`6884298a 881e            mov     byte ptr [esi],bl

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 000000006884298a (NPSWF32!native_ShockwaveFlash_TCallLabel+0x00000000000b0653)
   ExceptionCode: 80000001 (Guard page violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 0000000010110000

FAULTING_THREAD:  0000000000000000

BUGCHECK_STR:  HANG

PROCESS_NAME:  firefox.exe

ERROR_CODE: (NTSTATUS) 0xcfffffff - <Unable to get error code text>

NTGLOBALFLAG:  70

APPLICATION_VERIFIER_FLAGS:  0

DERIVED_WAIT_CHAIN:  

Dl Eid Cid     WaitType
-- --- ------- --------------------------
   0   14c4.160c Unknown                

WAIT_CHAIN_COMMAND:  ~0s;k;;

BLOCKING_THREAD:  000000000000160c

DEFAULT_BUCKET_ID:  APPLICATION_HANG_BusyHang

PRIMARY_PROBLEM_CLASS:  APPLICATION_HANG_BusyHang

LAST_CONTROL_TRANSFER:  from 0000000068842c1d to 000000006884298a

STACK_TEXT:  
WARNING: Stack unwind information not available. Following frames may be wrong.
0032e518 68842c1d 00000010 00000003 0032e778 NPSWF32!native_ShockwaveFlash_TCallLabel+0xb0653
00000000 00000000 00000000 00000000 00000000 NPSWF32!native_ShockwaveFlash_TCallLabel+0xb08e6


FOLLOWUP_IP: 
NPSWF32!native_ShockwaveFlash_TCallLabel+b08e6
00000000`68842c1d c1e608          shl     esi,8

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  NPSWF32!native_ShockwaveFlash_TCallLabel+b08e6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: NPSWF32

IMAGE_NAME:  NPSWF32.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  48640369

STACK_COMMAND:  ~0s ; kb

BUCKET_ID:  X64_HANG_NPSWF32!native_ShockwaveFlash_TCallLabel+b08e6

FAILURE_BUCKET_ID:  APPLICATION_HANG_BusyHang_cfffffff_NPSWF32.dll!native_ShockwaveFlash_TCallLabel

Followup: MachineOwner
---------

Comment 3

[Tyler Downer [He/Him]]

This is a mass search for bugs which are in the Firefox General component, are
UNCO, have not been changed for 500 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10 or later, create a fresh profile, http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you still see the issue, please update this bug. If the issue is gone, please set the status to RESOLVED > WORKSFORME.

Comment 4

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.