However, when I do the same process with a silverlight app (through
attaching to IE) I always get a "SRCSRV: The module 'SilverlightApplication1'
does not contain source server information." message. I can get stack traces
fine, but not source. I know the pdbs are properly indexed because I have ran
srctool on them.
I also looked at the symbol load information (by right clicking on the call
stack and selecting "symbol load information..") for the windows forms app
and silverlight app. They say the same things:
WindowsForms
D:\WindowsFormsApplication1.pdb: Cannot find or open the PDB file.
C:\p4root\Crystal\WindowsFormsApplication1\WindowsFormsApplication1\obj\Debug\WindowsFormsApplication1.pdb: Cannot find or open the PDB file.
D:\Symbols\WindowsFormsApplication1.pdb\406C415986A646DE85FA518FA66990611\WindowsFormsApplication1.pdb: Symbols loaded.
Silverlight
C:\Program Files (x86)\Microsoft Visual Studio
9.0\Common7\IDE\SilverlightApplication1.pdb: Cannot find or open the PDB file.
C:\p4root\Crystal\SilverlightApplication1\SilverlightApplication1\obj\Debug\SilverlightApplication1.pdb: Cannot find or open the PDB file.
D:\Symbols\SilverlightApplication1.pdb\C762FC1D74E34E8C909FF5C3625EB13C1\SilverlightApplication1.pdb: Symbols loaded.
but only the windows forms app actually loads source. I am at a loss here.
Is the source not loading a know issue with Silverlight?
What does !lmi SilverlightApplication1" show you? It will say if the pdb is
source-indexed or not.
.pat styles [microsoft]
"breeve" <bre...@newsgroups.nospam> wrote in message
news:EF3A3069-BBA1-4188...@microsoft.com...
Attached to IE and issued commands:
.sympath
SRV*D:\Symbols*\\blacklight\Symbols;http://msdl.microsoft.com/download/symbols
.srcpath SRV*D:\Symbols*\\blacklight\Symbols
.reload
.load C:\Program Files (x86)\Microsoft Silverlight\2.0.31005.0\sos
!bpmd SilverlightApplication1.dll SilverlightApplication1.Page.Button_Click
g
Now I hit my button on the silverlight app and I get a breakpoint:
Breakpoint 0 hit
eax=05793a2c ebx=00000000 ecx=09109e20 edx=09128fec esi=00556538 edi=0379f6bc
eip=05df0340 esp=0379f600 ebp=0379f618 iopl=0 nv up ei pl nz na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000206
05df0340 55 push ebp
Issue command !lmi SilverlightApplication1 and
!lmi SilverlightApplication1
Loaded Module Info: [silverlightapplication1]
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\Program Files (x86)\TortoiseSVN\bin\intl3_svn.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
c:\program files (x86)\google\googletoolbar1.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\Program Files (x86)\Google\GoogleToolbarNotifier\4.1.805.4472\swg.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\Program Files (x86)\TortoiseSVN\bin\tortoisesvn.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\Program Files (x86)\McAfee\VirusScan Enterprise\scriptcl.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\Program Files (x86)\Java\jre1.6.0_07\bin\ssv.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\Program Files (x86)\TortoiseSVN\iconv\windows-1252.so -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\Program Files (x86)\TortoiseSVN\iconv\utf-8.so -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\Program Files (x86)\TortoiseSVN\iconv\_tbl_simple.so -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\Program Files (x86)\TortoiseSVN\bin\libapriconv_tsvn.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\Program Files (x86)\TortoiseSVN\bin\libaprutil_tsvn.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\Program Files (x86)\TortoiseSVN\bin\libapr_tsvn.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\Windows\SysWOW64\mshtml.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\Program Files (x86)\Microsoft Office\Office12\msohevi.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
C:\Windows\system32\slc.dll -
silverlightapplication1 not found
Not sure why the last line says silverlightapplication1 not found. I looked
in the modules under Debug>>Modules... and I don't see
silverlightapplication1 listed\
Thanks for your help so far.
It will list the source server information for the pdb.
.pat styles [microsoft]
"breeve" <bre...@newsgroups.nospam> wrote in message
news:BAC356CE-0E32-4039...@microsoft.com...
Here is exactly what I did for the Silverlight case:
1. Browse to simple silverlight application in IE (hosted on another machine)
2. Use Debug>>Attach to Process.
3. Select IE from available process and make sure Silverlight code is
selected to debug.
4. Select attach.
5. Set a break point using the breakpoints window to a function that gets
run when a button is pressed on the silverlight app.
6. Go to IE and press silverlight button.
7. Break point is hit. (Get dialog to browse to source)
8. Look at call stack, right click and select Symbol load information and get:
C:\Program Files (x86)\Microsoft Visual Studio
9.0\Common7\IDE\SilverlightApplication1.pdb: Cannot find or open the PDB file.
C:\p4root\Crystal\SilverlightApplication1\SilverlightApplication1\obj\Debug\SilverlightApplication1.pdb: Cannot find or open the PDB file.
D:\Symbols\SilverlightApplication1.pdb\1CFB6FA213CB42FD96C6B5026B541ECC1\SilverlightApplication1.pdb: Symbols loaded.
9. Run srctool on the last location pdb where symbols are loaded and I get:
D:\Symbols\SilverlightApplication1.pdb\1CFB6FA213CB42FD96C6B5026B541ECC1\Silverl
ightApplication1.pdb: 4 source files are indexed
Along with all the perforce commands to retrieve the source files. The
srctool output looks the same as my windows forms example. I don't see any
differences except this is silverlight?
The reason I originally suggested some WinDbg commands is because this forum
supports WinDdb and not VS. I was presuming that you were using WinDbg.
Also I have no specific knowledge of VS so you might be better served by
another newsgroup. That said, should be a way to get debug information from
VS that shows it trying to execute the Source Server commands? I am told
that you can to this by changing some settings...
Under tools->options->Debugging->General there is a subitem under "Enable
Source Server support" to "Print source server diagnostics messages to the
output window"
Sometimes I wonder what you mean by "Silverlight code". Silverlight is a
Microsoft product and I don't believe the source is available to you. If
you are talking about code that you wrote that calls Silverlight, then, I
see absolutely no reason for code you wrote that calls Silverlight to be any
less available by Source Server then code you write that calls WinForms.
Please understand that I have no knowledge of these libraries and there may
be something going on that I am not aware of.
What seems more likely is that the issue is with the actual bits. Why don't
you put some Silverlight calls in the WinForm client code you wrote and see
if the source is accessable. Don't split the DLLs. Just integrate them
together. If it starts to work, then you know the issue is related to the
separate build targets.
.pat styles [microsoft]
"breeve" <bre...@newsgroups.nospam> wrote in message
news:BACE6071-E7BD-434A...@microsoft.com...
> Under tools->options->Debugging->General there is a subitem under "Enable
> Source Server support" to "Print source server diagnostics messages to the
> output window"
I have those options turned on in VS.
> Sometimes I wonder what you mean by "Silverlight code". Silverlight is a
> Microsoft product and I don't believe the source is available to you.
I am setting up a symbol server for our own source which builds on top of
the Silverlight runtime. I don't want to get the source for the silverlight
code itself or its libraries, just ours from our symbol server.
>If you are talking about code that you wrote that calls Silverlight, then, I
> see absolutely no reason for code you wrote that calls Silverlight to be any
> less available by Source Server then code you write that calls WinForms.
Yes, this is what I am talking about and seems weird. Somehow, the code I
wrote that calls Silverlight is not available from our source server but the
windows forms is. I followed the exact same process for running ssindex and
symstore when adding both sources (windowsforms and silverlight).
> What seems more likely is that the issue is with the actual bits. Why don't
> you put some Silverlight calls in the WinForm client code you wrote and see
> if the source is accessable.
I agree that it maybe an issue with the Silverlight bits (debugging tools
bits?). Silverlight code does not run on the desktop. Silverlight is a web
based plugin framework like Flash. I think I might try the silverlight forms.
Can you email me privately at pat.s...@microsoft.com? I have a lot of
questions for you.
.pat styles [microsoft]
"breeve" <bre...@newsgroups.nospam> wrote in message
news:29B74551-904F-4436...@microsoft.com...
I think you would want
.sympath SRV*D:\Symbols*\\blacklight\Symbols*http://msdl.microsoft.com/download/symbols
rather than
.sympath SRV*D:\Symbols*\\blacklight\Symbols;http://msdl.microsoft.com/download/symbols
Regards,
Philip McGraw