This document summarizes a meeting of the Portuguese SharePoint Community held on June 12, 2010. The agenda included an overview of debugging, debugging tools, and next steps. It defines debugging as methodically finding and reducing bugs to make a program or hardware behave as expected. It discusses various debugging techniques like screen dumps, logs, code debugging in Visual Studio, web debugging with tools like Fiddler, and runtime debugging using the Windows kernel and tools like Windbg. Further reading materials are also provided.
4. DefinitionIn wikipedia:Debuggingis a methodical process of finding and reducing the number of bugs, or defects, in a computer program or a piece of electronic hardware, thus making it behave as expected. … it involves numerous aspects, including: interactive debugging, control flow, integration testing, log files, monitoring, memory dumps, Statistical Process Control, and special design tactics to improve detection while simplifying changes.
5. DefinitionIn wikipedia:Debuggingis a methodical process of finding and reducing the number of bugs, or defects, in a computer program or a piece of electronic hardware, thus making it behave as expected. … it involves numerous aspects, including: interactive debugging, control flow, integration testing, log files, monitoring, memory dumps, Statistical Process Control, and special design tactics to improve detection while simplifying changes.
6. Bottom lineDebug = Solve a problemTechniques + Tools = gather information
13. Runtime debug: kernel outputMessages are thrown to the kernelAny tool can plug into the kernel and read the messagesSysinternals Debug view
14. Runtimedebug: kernel (windbg)Attach directly to a processIdentify process with windbgMain commands.loadby sos mscorwksSxe clr!g (F5)!pe!do | !da!dso-clrstack –a!analize
#11: Event logs: * abrir o event viewer e mostrar alguns eventosIIS * abir o inetmgr * entrar num site e ver a localização dos seus logs * ir por file system e abrir os logsULS * abrir os logs e mostrar o tipo de informação que lá existe * abrir a central administration e mostrar a localização da configuração dos logs
#12: Sample1.aspx – mostrar um estoiro com informação.Sample1_ok.aspx – mostra página OKSample