trace

So I'm probably missing the obvious here, but what actually is the difference between the functionality of the TraceSwitch and SourceSwitch classes? They both give identical summary descriptions: Provides a multilevel switch to control tracing and debug output without recompiling your code. Are the Remarks sections are oddly similar to my eyes. Could someone please clarify the difference in their functionality and usage cases? (For completeness, I'm using switches with my TraceSource object, rather than the old static Trace class, though I doubt it makes much difference.) GraemeF The

I am developing a program under Linux. For debugging purposes I want to trace all calls from my program to a certain (preferably shared) library. (I do not want to trace calls happening inside the library.) For syscalls there is strace. Is there any instrument to trace calls to a shared library? The tool you are looking for is called ltrace . It allows to trace any call from the program to all (or a set of given) libraries. For example, the following call will list any call to an external function loaded by a shared library: $> ltrace ls / __libc_start_main(0x4028c0, 2, 0x7fff1f4e72d8,

I found this in some production login code I was looking at recently... HttpContext.Current.Trace.Write(query + ": " + username + ", " + password)); ...where query is a short SQL query to grab matching users. Does this have any sort of performance impact? I assume its very small. Also, what is the purpose of this exact type of trace, using the HTTP Context? Where does this data get traced to? Thanks in advance! JaredPar Yes it will have a performance impact whenever the TRACE conditional compilation constant is defined during build. Doing anything has some type of impact :) As to whether or

I've been trying to setup trace logging for a while and I simply can't get it to work properly. It doesn't help they are so many wrong/outdated articles on this topic. But please can someone give me a good and practical setup for trace logging & viewing for Azure (1.6) All I want to do is the ability to capture and view trace messages from my app. I started out with standard DiagnosticMonitorTraceListener but that ends up in table storage. I can't for the life of me figure out how I'm supposed to interact with the Logs in table storage. In Visual Studio I can 'view' it but it's so extremely

My VS 2013 output window is full of this: iisexpress.exe Information: 0 : Request, Method=GET, Url=http://localhost:51741/api/Clients/?$filter=UniqueName eq '6269', Message='http://localhost:51741/api/Clients/?$filter=UniqueName eq '6269'' iisexpress.exe Information: 0 : Message='Clients', Operation=DefaultHttpControllerSelector.SelectController iisexpress.exe Information: 0 : Message='MyProj.Controllers.ClientsController', Operation=DefaultHttpControllerActivator.Create iisexpress.exe Information: 0 : Message='MyProj.Controllers.ClientsController', Operation=HttpControllerDescriptor

I am trying to use TraceCompass in order to further investigate my system trace. For that purpose, you need CTF format and there are two possible ways to obtain it in Linux, afaik: Using LTTng for tracing and using CTF format from that Using 'perf data convert' in order to create CTF data from perf.data I have been trying to use the second option as the first one requires installation of tracepoints and what I got from perf is simply enough for me. So assuming I have my perf.data available, Applying perf data convert --to-ctf=./ctf resulted in: No version support compiled in. Digging into the

I'm trying to display some TraceSource logging information to the Azure emulator ( consoley ) window. None of the TraceSource lines are displayed. Only the stock Trace lines and various low level azure messages. Here's my steps to repo, including code snippets: File -> New -> Cloud Service (SDK 2.0) -> (add worker role). Add a TraceSource to the WorkerRole. Update the app.config with tracing data. Play/Publish. NOTE all the other default code is in there, such as the .csfg which says to use UseDevelopmentStorage=true etc Worker Role code. This is the STOCK DEFAULT CODE with my TraceSource

I have the problem debugging an complicated recursive function I'm using the idiom: dbg:tracer(),dbg:p(all,c),dbg:tpl(Mod,Fun1,x),dbg:tpl(Mod,Fun2,x)... This gives me a flat list of calls to all functions where it is very hard to find out which return belongs to which call. Is there a easy way to make this more readable e.g. by indenting. I could just post process the text produced and indent for each call, and outdent for each return, but this sounds not very elegant to me. In the meantime I figured it out how to do this, its actually not too hard. To have a process handling the trace message