Debug

Although Flex Builder and Eclipse do have nice debug utilities built in, today I needed a function/method in Actionscript to display into the current application some variables’ content. So I started to implement a var_dump alike function (var_dump from PHP language). So I started and I made the Debug class that will implement the static dump [...]

If you try to activate the feature using stsadm command you will not be able to debug the feature receiver assemblies.Open the Site collection features inSite Actions ->Site Settings ->Modify All Site Settings ->Site Collection Administration -> Site Collection featuresAttach the w3wp.exe process in visual studio.Place breakpoints.Then Activate the feature in site collection features

An issue where registry reflection was not happening while installing 32bit Office under the system account. This required looking into both the 32bit Office code and the Wow64 code where the registry reflection is implemented.  When attaching to the Wow64 process using the 32bit debugger it’s like debugging a 32bit process on the 32bit machine; [...]

Mais uma descoberta no mundo do Playstation 3. A novidade agora é que conseguiram instalar firmwares de Debug em máquinas “retail” (consoles vendidos em loja) normais. Apesar da novidade, ainda não dá pra fazer muita coisa com um PS3 com um firmware de debug instalado, mais já é uma avanço de acordo com os especialistas [...]

Today I installed Astro! What I did to be able to still develop and debug flash player 9 applications? I installed the Flash Player 10 just for Firefox and for debug I'm using IE. You can inverse it and install the ActiveX for IE and keep Firefox with the flash player 9. The links to [...]

Changelog============================================================================Revision 6943 - Directory ListingModified Tue May 6 16:54:13 2008 UTC (3 hours, 54 minutes ago) by raspopovAdded Up, Down, Home and End keys to log window.============================================================================Revision 6942 - Directory ListingModified Tue May 6 03:10:55 2008 UTC (17 hours, 37 minutes ago) by raspopovRemoved invalid ASSERT().============================================================================Revision 6941 - Directory ListingModified Mon May 5 14:38:58 2008 UTC (30 hours, 9 minutes ago) by raspopovAdded shell menu cache.============================================================================Revision 6940 - Directory ListingModified Mon May 5 12:28:00 2008 UTC

Update: As reviewed here, installing Visual Studio 2008 will enhance QTP's debug capabilities. Sometimes, however, installing VS2008 may be a non-option, as it radically changes the test-machine you're working on. Luckly, as Motti has noted on the original article, you don't really need to install VS2008, but only a small DLL called PDM.DLL. You simply obtain the DLL (by downloading VS2008 express or via any other source), and copy it to "C:\Program Files\Common Files\Microsoft Shared\VS7DEBUG" (make sure to make a backup of the original DLL first!). Now, write the following command in the RUN menu (or in CMD) : RegSVR32 C:\Program Files\Common Files\Microsoft Shared\VS7DEBUG\pdm.dll You may need to restart the machine, and presto! Upgraded debugging capabilities, without the tires

Yesterday I was in for a very pleasant surprise - I've just installed Visual Studio 2008, and was working on a QTP test, when I've noticed a something strange with QTP's Debug view. Usually when you add a watch to an Object, QTP will present it as an enigmatic "<Object>", with no further description. If you're really lucky, it will be accompanied by a small "+" sign, which will expose some of the object's properties. In this example, oDic is a Scripting.Dictionary object I've created. You can see that it has a .Count property, Item property, etc.: It's important to note that a Scripting.Dictionary object has many properties and methods that are not shown in QTP's debug window - .Keys, .Items, .Remove, .Add etc. However, after installing VS2008, my debug view presen

Tramite la reflection è possibile conoscere se un determinato assembly è stato compilato in modalità debug o release, andando a spulciare nella lista degli attributi: 1: Private Function VerifyDebug() As Boolean 2: Dim assembly As Assembly = Reflection.Assembly.LoadFile("path assembly") 3: Dim attributes() As Object = assembly.GetCustomAttributes(True) 4: If Not (attributes Is Nothing) AndAlso (attributes.Length > 0) Then 5: For i As Integer = 0 To attributes.Length - 1 6: If (attributes(i).GetType() Is GetType(System.Diagnostics.DebuggableAttribute)) Then 7: Return True 8: End If 9: Next 10: End If 11: Return False 12: End FunctionCon il ciclo sugli attributi vado a verificare se è presente l'attributo DebuggableAttribute, attributo non presente se l'assembly è stato generato in modalità release.

How do I debug JavaScript?There are not that many tools out there that will support both client-side and server-side debugging. I am certain this will change as AJAX applications proliferate. I currently do my client-side and server-side debugging separately. Below is some information on the client-side debuggers on some of the commonly used browsers.* Firefox/Mozilla/Netscape - Have a built in debugger Venkman which can be helpful but there is a Firefox add on known as FireBug which provides all the information and AJAX developer would ever need including the ability to inspect the browser DOM, console access to the JavaScript runtime in the browser, and the ability to see the HTTP requests and responses (including those made by an XMLHttpRequest). I tend to develop my applications initially on Firefox using Firebug then venture out to the other browsers.* Safari - Has a debugger which needs to be enabled. See the Safari FAQ for details.* Internet Explorer - There is MSDN Documentatio

Il francese Jean-Fabrice Rabaute ha realizzato DebugBar, un plugin per il browser Internet Explorer che consente di effettuare debug del DOM.Se vogliamo fare paragoni è simile a Firebug (ottima estensione per Firefox).Il tool è orientato soprattutto per il debug del DOM e dei CSS, e supporta dalla versione 5 alla 7 di IE.Altro plugin interessante, creato dallo stesso autore è Companion.JS dedicato invece per il debugger di javascript.

Download this file from here --> Debug.sapDrag and drop this onto the Popup and the you can start your debug from there. This is a small text file and contains few lines of text to initiate debugging.[FUNCTION]Command=/HTitle=DebuggerType=SystemCommand~~~ end of post ~~~---------------------ABAPer, mail: abap.community@gmail.com http://abaplearner.blogspot.com

Let's say you are using a 3rd Party Library like ELMAH in your web site project to handle unhandled exceptions and it's throwing an exception and you don't know why.  Since the code is open source, you would LOVE to see what line its crashing on and then submit your changes to the project so that others can benefit from the fix you made.  It gives you that good feeling, right? Well, unfortunately, you put the compiled DLL in the bin folder and when it crashes, it just crashes and burns. How can you see the source code?  Simple!  Compile the source code on your machine, and copy the PDB ("Debugging Database") file to your bin folder along with the DLL, and then your web site crashes while in debug mode, it will go to the exact folder on your file system where the DLL was compiled from

In my previous post I started to talk about how you can see the same trace messages you were used from developing but this time in the "Release". This is done with the help of the Log class (mx.logging.Log). Let's take a look at some pieces of code (full code can be provided per request).   private var myTarget:ILoggingTarget; myTarget = new TraceTarget(); Log.addTarget(myTarget); var myLogger:ILogger = Log.getLogger(category); myLogger.log(0,message); The first 2 lines create a variable of type TraceTarget. Then it is added to the loggers list by calling Log.addTarget(myTarget) . After that all we have to do is log the message: myLogger.log(0,message); . How can we use this method to send the log output to a remote machine? Simple we have to create our own logger:   package com.qbic.logging { import flash.events.Event; import flash.net.XMLSocket;   import mx.logging.LogEvent; import mx.logging.targets.LineFormattedTarget;   internal final class remoteTarget exte

One of the most common problems in developing new applications is their debugging. There are several methods to do this in Flex (trace, alert - like somebody once said: "Alert till death"). But what happens if you want the same logging that you had on your work environment to also be available when the application is distributed to the customer? There are several methods to do this: logging into a field in the application, logging to the customer database (if the application uses a database) or using TraceTargets. There may be other methods to do this, but this are the main ones. I will not talk about the database approach, but I will concentrate on the TraceTarget approach. Imagine you have an application that is distributed to a lot of clients and one of them tells you he has a problem. In this case you can ask him for a description of the problem and try to replicate it. That often is not successful. What if you could instruct the application you developed to send you the trace

Tags: ActionScript, ActionScript 3.0, crawler, CS3, Feed Rss, firefox, Flash, Flash Player, google, Google Calendar, http, ie7, Internet, Internet Explorer, PHP, protocolli, rss, Sviluppo, user agentUna considerazione, ovvia ma sottovalutata, durante lo sviluppo di applicazioni in Adobe Flash: la differenza tra il Player utilizzato per il testing all’interno dell’IDE Flash e l’oggetto (ActiveX o EMBED) usato dal nostro browser. Chi possiede la versione “Macromedia” Flash MX (la versione 8 per intenderci, ma questo discorso in realtà vale per qualsiasi versione di Flash…) quando sviluppa un filmato e lo prova all’interno dell’IDE Flash manda in esecuzione il Player legato al pacchetto di sviluppo. Quando poi si pubblica il filmato sulla rete e lo si “prova” con il Player Flash del browser si potrebbero riscontrare alcune - sostanziali - differenze!   Flash Player Release La prima differenza, forse quella più imp

Per il debug di script javascript ho sempre fatto affidamento all'estensione di Firefox: FireBug, ma è possibile farlo anche con solo VS 2003 o VS 2005.Dopo aver attivato l'opzione su Internet Explorer: Debugging degli script( Strumenti => Opzioni Internet => Avanzate => Esplorazione), ed aver lanciato in modalità debug l'applicazione Asp.Net dall'ambiente di sviluppo VS 2003:si può attivare Script Explorer( Ctrl+Alt+N):e quindi poter inserire breakpoints nella sezione script:

In Part 1 we've seen what can cause a BSOD and what information we can collect after it happens, so we could investigate the problem. Well, Microsoft gives us the Debugging Tools for Windows toolkit.Go to the link, and download the latest version that is appropriate to your system (i.e. x86/64bit). This toolkit allows us to diagnose the memory dump files that Windows saved during the BSOD and hopefully pinpoint the root cause of the problem.While debugging the dump files, the tools compare the drivers' and operating files' information from the memory collected in the dump file, to a database of "symbols" from Microsoft. the Symbols database will most likely be used from the internet using Microsoft Symbols server, but can also be downloaded and used offline (it's a huge file- only download if you must...). Let The Debugging Begin!At first we run the WinDbg utility from the Debugging Tools for Windows we just installed.In the File menu - "Open Crash Dump" - Choose you Minidump or Me

We've all seen it before... Suddenley the screen turns blue and an error appears saying something like "it appears you won't be going to sleep early tonight..."Luckily there are easy ways to make some sense of that technical jargon MS gives us in a case of a BSOD.First lets TRY and understand what can cause your problem:Bad Hardware (RAM, Disk, PCI devices, USB Devices, Temperature etc..).Bad Software (Drivers, Anti-viruses etc...).Bad Windows (Registry corruption, missing files etc...).The basic BSOD message includes:The standard Stop error message "Windows has encountered a problem... bla bla bla..."Error Description: IRQ_NOT_LESS_OR_EQUALError Code: "0x0000008E" and some more memory addresses in ( )Optional file/driver name that might caused the problem.What we are going to do is collect as much information we can so we can investigate the BSOD and find the root cause. The information we can collect depends if we saw the BSOD ourselves or just heard about it from the end-user, if

Debug has been included in every version of MS-DOS as well as Windows. When running any of the debug routines it is recommended that if you have Windows that you exit or shut down to get into a real DOS prompt (unless you're running Windows ME, Windows 2000, Windows XP, or later versions).Once at the MS- DOS prompt, run through the below example, this example is perfectly fine to run on any PC Computer running MS-DOS / Windows and will not harm anything.Type debug and press enter.This should get you to a - (small dash). This is the debug prompt.At the - type d40:00 and press enter; this will return several lines of information.After the feedback you will be back to the debug prompt.To exit out of debug type q and press enter. This will return you back to the MS-DOS prompt.In some of the below debug routines you will notice that a "g" is typed, then "q". G tells the computer that the code type is not self executing and must be run at this point. If completed, the program will return Pr

I usually download Flash games with the help of my trusty Opera Browser via Tools > Advanced > Cache and search for either .swf or the domain name of the server hosting the Flash game. It's easy to get the Flash game this way if all the content has been packaged into a single .swf file. For games which are contained in multiple swfs, you have to download all associated .swfs and replicate the directory structure. Anyway, this post is not about downloading multi-swf games so I will leave it to another time. Once I downloaded a Flash game, I used to drag and drop it into any browser (usually opera) with the Flash plugin installed and play the game offline. Most games work perfectly fine for me this way except that the Flash plugin for my Opera browser doesn't work too well and guzzles up a lot of memory after a while.I chanced upon this page on Adobe Flash Player Support Center where Adobe offers free downloads of "Projector Content Debuggers / Debug Players" which are essentially the

  Rafael Mizrahi, the QA Lead at Mainsoft sent in this cool video of a Nintendo Wiimote that is used to debug .NET code! I wonder if the bluetooth Wiimote interface to the computer is being handled using Carl Kenner’s Glovepie or if Rafael created his own from scratch? Either way, Great job!

Ha relatos no cena homebrew que algumas almas mais afortunadas tiveram acesso a uma versao debug do firmware 1.80 do Playstation 3, o ultimo lançado pela Sony. Isso teoricamente pode levar a muitas possibilidades, como por exemplo loaders, bugs para que programas possam ser executados com... [Clique no titulo da noticia para conteudo completo e links]

Me parece tremendamente irónico que el día que Microsoft nos dice que no puede facilitarnos una 360 Debug para ejecutar la beta de The Darkness que tan amablemente la gente de Take 2 nos ha ofrecido, se haya filtrado el firmware de las PS3 capaces de ejecutar copias sin firmar. Estas copias no son backups, sino las utilizadas por las compañías para hacer llegar a las publicaciones del sector juegos inacabados en fase beta o incluso lanzamientos finalizados en un formato más barato para ellas que una copia retail, con caja, instrucciones y demás. No hay que ser Nosferatu para ver más cerca que nunca el día en el que sea posible ejecutar backups en PlayStation 3, la última consola que quedaba virgen en esta generación. Recordemos que Xbox 360 (firmware lector) y Wii (chip) ya cayeron previamente. Fuente: FayerNews

I recently received a bug report for an ASP.NET site I've been maintaining but when I went off to test out the problem running the site through Visual Studio eveything worked fine. Slightly confused, I went back to the live site and immediately reproduced the problem. So I thought the problem must be caused by the site not being in sync with the the development box so I uploaded the latest code. The problem was still occurring... I was fairly unfamiliar with the code so I started stepping through it. You've no doubt guessed the problem by now from the title of this post. There was some code wrapped in an #if DEBUG directive that actually overrode the parameters passed into the page via a query string. I removed that and the problem on the live site was reproducible in Visual Studio. But I wasted an hour or so getting to the bottom of it. So the moral of the story is don't change behaviour of your code with #if DEBUG statements. The only use I've found for #if DEBUG i

The Debug Diagnostic Tool (DebugDiag) is designed to assist in troubleshooting issues such as hangs, slow performance, memory leaks or fragmentation, and crashes in any Win32 user-mode process. The... [[ This is a content summary only. Visit my website for full links, other content, and more! ]]