生成/创建mdump文件在我的应用程序 [英] Generate / create mdump files for in my app
问题描述
林寻找一种方式,在我的应用程序simular什么 ProcDump生成小型转储文件的确但prefarably的代码,并没有提取3dparty工具来做到这一点。
Im looking for a way to generate minidump files in my applications simular to what ProcDump does but prefarably with code and not having to extract a 3dparty tool to do it.
的主要原因不希望使用的 ProcDump 是:结果
1)二进制会大大增加的大小(这是一个问题,因为我的应用程序是免费的,和带宽是不是免费的)。结果
2)感觉很脏。结果
3)没办法我只能端口应用经营的旅馆的Windows Mobile。结果
The main reasons for not wanting to use ProcDump is:
1) Size of the binary would increase greatly ( This is a problem because my apps are freeware, and bandwith is not free).
2) Feels dirty.
3) No way i can port that app to run inn windows mobile.
我的要求是:结果
1)能够生成mdump文件的尤物碰撞结果
2) Abilityt做暂停的应用做了转储和contiune将奖金结果。
结果
。如果这不是真的一个选项,有没有办法让在目前情况下动态地?
My requirements are:
1) Ability to generate mdump files in a fatale crash.
2) Abilityt to do "pause" the app do a dump, and contiune would be a bonus
.
If this is not realy a option, is there a way to get the values of local varibales in the current context dynamicly?
附注:
我做鱼翅 D此文章,但它很老,所以我让即时通讯犹豫立足我对它的工作。结果
似乎要么是与IE 9或与网站的问题,所以我不得不使用标签的问题。
Side note:
I did find this article, but its very old so i so im hesitant to base my work of it.
There seems to either be a issue with IE 9 or with the site, so i had problems with tags.
推荐答案
因此,有一些新想法,并符合下列目标之一的解决方案:
So there is one solution that comes to mind and meets the following goals:
- 的二进制文件的大小会被周围的30万增加
- 能够生成mdump文件放在一个荡妇崩溃。
- 能力做暂停的应用做了转储和contiune将奖金
我给这要求一个完整的未知:
I'll give this requirement a complete unknown:
- 没办法我只能端口应用经营的旅馆的Windows Mobile。
那么,有什么解决办法?
整合您从微软样品需要MDbg.exe提供所需的零件你与重视,转储,并从崩溃进程脱离了刚刚在时间'调试
Integrate the required parts you need from the Microsoft Sample for MDbg.exe to provide you with a 'just-in-time' debugger that attaches, dumps, and detaches from the crashing process.
第1步 - 通过下载源代码到MDBG启动从这里开始: HTTP: //www.microsoft.com/downloads/en/details.aspx?FamilyID=38449a42-6b7a-4e28-80ce-c55645ab1310&DisplayLang=en
Step 1 - Start by downloading the source code to the mdbg from here: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=38449a42-6b7a-4e28-80ce-c55645ab1310&DisplayLang=en
第2步 - 创建一个'崩溃'处理程序生成一个调试器进程并等待完成。我用下面的代码几行用一些额外的参数重新启动相同的exe文件来调用调试器和输出的XML文件到std ::出来。
Step 2 - Create a 'crash' handler that spawns a debugger process and waits for completion. I used the following few lines of code to re-launch the same exe with a few extra arguments to invoke the debugger and output an xml file to std::out.
string tempFile = Path.GetTempFileName();
Mutex handle = new Mutex(true, typeof(Program).Namespace + "-self-debugging");
try
{
Process pDebug = Process.Start(typeof(Program).Assembly.Location,
"debug-dump " + Process.GetCurrentProcess().Id + " " + tempFile);
if (pDebug != null)
pDebug.WaitForExit();
}
catch { }
finally
{
handle.ReleaseMutex();
}
Console.WriteLine(File.ReadAllText(tempFile));
第3步 - 写入调试转储程序,这可能是在同一个EXE或在不同的EXE 。您需要引用(或包括从源)的原始,corapi',并从样品'mdbgeng'的模块。然后添加几行到您的Main():
Step 3 - Write the debug dump routine, this can be in the same exe or in a different exe. You will need to reference (or include the source from) the 'raw', 'corapi', and 'mdbgeng' modules from the sample. Then add a few lines to your Main():
public static void Main(string[] args)
{
if (args.Length > 0 && args[0] == "debug-dump")
{ //debug-dump process by id = args[1], output = args[2]
using (XmlTextWriter wtr = new XmlTextWriter(args[2], Encoding.ASCII))
{
wtr.Formatting = Formatting.Indented;
PerformDebugDump(Int32.Parse(args[1]), wtr);
}
return;
}
//... continue normal program execution
}
static void PerformDebugDump(int process, XmlWriter x)
{
x.WriteStartElement("process");
x.WriteAttributeString("id", process.ToString());
x.WriteAttributeString("time", XmlConvert.ToString(DateTime.Now, XmlDateTimeSerializationMode.RoundtripKind));
MDbgEngine e = new MDbgEngine();
MDbgProcess me = e.Attach(process);
me.Go().WaitOne();
try
{
x.WriteStartElement("modules");
foreach (MDbgModule mod in me.Modules)
x.WriteElementString("module", mod.CorModule.Name);
x.WriteEndElement();
foreach (MDbgThread thread in me.Threads)
{
x.WriteStartElement("thread");
x.WriteAttributeString("id", thread.Id.ToString());
x.WriteAttributeString("number", thread.Number.ToString());
int ixstack = -1;
foreach (MDbgFrame frame in thread.Frames)
{
x.WriteStartElement("frame");
x.WriteAttributeString("ix", (++ixstack).ToString());
x.WriteAttributeString("loc", frame.ToString(String.Empty));
string valueText = null;
x.WriteStartElement("args");
try
{
foreach (MDbgValue value in frame.Function.GetArguments(frame))
{
x.WriteStartElement(value.Name);
x.WriteAttributeString("type", value.TypeName);
try { x.WriteAttributeString("value", value.GetStringValue(1, false)); }
finally { x.WriteEndElement(); }
}
}
catch { }
x.WriteEndElement();
x.WriteStartElement("locals");
try
{
foreach (MDbgValue value in frame.Function.GetActiveLocalVars(frame))
{
x.WriteStartElement(value.Name);
x.WriteAttributeString("type", value.TypeName);
try { x.WriteAttributeString("value", value.GetStringValue(1, false)); }
finally { x.WriteEndElement(); }
}
}
catch { }
x.WriteEndElement();
x.WriteEndElement();
}
x.WriteEndElement();
}
}
finally
{
me.Detach().WaitOne();
}
x.WriteEndElement();
}
示例输出
<process id="8276" time="2010-10-18T16:03:59.3781465-05:00">
<modules>
<module>C:\Windows\assembly\GAC_32\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.dll</module>
...etc
</modules>
<thread id="17208" number="0">
<frame ix="0" loc="System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop (source line information unavailable)">
<args>
<this type="System.Windows.Forms.Application.ComponentManager" value="System.Windows.Forms.Application.ComponentManager
 oleComponents=System.Collections.Hashtable
 cookieCounter=1
 activeComponent=System.Windows.Forms.Application.ThreadContext
 trackingComponent=<null>
 currentState=0" />
<dwComponentID type="N/A" value="<N/A>" />
<reason type="System.Int32" value="-1" />
<pvLoopData type="System.Int32" value="0" />
</args>
<locals>
<local_0 type="System.Int32" value="0" />
<local_1 type="System.Boolean" value="True" />
<local_2 type="System.Windows.Forms.UnsafeNativeMethods.IMsoComponent" value="<null>" />
<local_3 type="N/A" value="<N/A>" />
<local_4 type="N/A" value="<N/A>" />
<local_5 type="N/A" value="<N/A>" />
<local_6 type="System.Windows.Forms.Application.ThreadContext" value="System.Windows.Forms.Application.ThreadContext
 contextHash=System.Collections.Hashtable
 tcInternalSyncObject=System.Object
 totalMessageLoopCount=1
 baseLoopReason=-1
 currentThreadContext=System.Windows.Forms.Application.ThreadContext
 threadExceptionHandler=System.Threading.ThreadExceptionEventHandler
 idleHandler=<null>
 enterModalHandler=<null>
 leaveModalHandler=<null>
 applicationContext=System.Windows.Forms.ApplicationContext
 parkingWindow=<null>
 marshalingControl=System.Windows.Forms.Application.MarshalingControl
 culture=<null>
 messageFilters=<null>
 messageFilterSnapshot=<null>
 handle=912
 id=17208
 messageLoopCount=1
 threadState=1
 modalCount=0
 activatingControlRef=<null>
 componentManager=System.Windows.Forms.Application.ComponentManager
 externalComponentManager=False
 fetchingComponentManager=False
 componentID=1
 currentForm=Program.MainForm
 threadWindows=<null>
 tempMsg=System.Windows.Forms.NativeMethods.MSG
 disposeCount=0
 ourModalLoop=False
 messageLoopCallback=<null>
 __identity=<null>" />
<local_7 type="N/A" value="<N/A>" />
<local_8 type="N/A" value="<N/A>" />
<local_9 type="N/A" value="<N/A>" />
<local_10 type="N/A" value="<N/A>" />
<local_11 type="N/A" value="<N/A>" />
<local_12 type="N/A" value="<N/A>" />
<local_13 type="System.Boolean" value="False" />
<local_14 type="System.Windows.Forms.NativeMethods.MSG[]" value="array [1]
 [0] = System.Windows.Forms.NativeMethods.MSG" />
</locals>
</frame>
<frame ix="1" loc="System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner (source line information unavailable)">
<args>
<this type="System.Windows.Forms.Application.ThreadContext" value="System.Windows.Forms.Application.ThreadContext
 contextHash=System.Collections.Hashtable
 tcInternalSyncObject=System.Object
 totalMessageLoopCount=1
 baseLoopReason=-1
 currentThreadContext=System.Windows.Forms.Application.ThreadContext
 threadExceptionHandler=System.Threading.ThreadExceptionEventHandler
 idleHandler=<null>
 enterModalHandler=<null>
 leaveModalHandler=<null>
 applicationContext=System.Windows.Forms.ApplicationContext
 parkingWindow=<null>
 marshalingControl=System.Windows.Forms.Application.MarshalingControl
 culture=<null>
 messageFilters=<null>
 messageFilterSnapshot=<null>
 handle=912
 id=17208
 messageLoopCount=1
 threadState=1
 modalCount=0
 activatingControlRef=<null>
 componentManager=System.Windows.Forms.Application.ComponentManager
 externalComponentManager=False
 fetchingComponentManager=False
 componentID=1
 currentForm=Program.MainForm
 threadWindows=<null>
 tempMsg=System.Windows.Forms.NativeMethods.MSG
 disposeCount=0
 ourModalLoop=False
 messageLoopCallback=<null>
 __identity=<null>" />
<reason type="System.Int32" value="-1" />
<context type="System.Windows.Forms.ApplicationContext" value="System.Windows.Forms.ApplicationContext
 mainForm=Program.MainForm
 userData=<null>
 ThreadExit=System.EventHandler" />
</args>
<locals>
<local_0 type="System.Windows.Forms.Form" value="<null>" />
<local_1 type="System.Boolean" value="False" />
<local_2 type="N/A" value="<N/A>" />
<local_3 type="N/A" value="<N/A>" />
<local_4 type="N/A" value="<N/A>" />
</locals>
</frame>
... etc
</thread>
</process>
既然你有调试器的全部功能并没有什么从编写尽可能多或尽可能少你喜欢阻止你,但上面的例子应该让你开始。
Since you have the full power of a debugger there is nothing stopping you from writing as much or as little as you like, but the above example should get you started.
更新
这工作原理与NET 2.0和/或没有任何进一步的依赖性3.5运行时。
This works with the .Net 2.0 and/or 3.5 runtime without any further dependencies.
这可以调试的.Net在.NET 4.0的进程中运行2.0 / 3.5的代码,但是,它不会与4.0(还)工作。
This can debug .Net 2.0/3.5 code running in a .Net 4.0 process; however, it does not work with 4.0 (yet).
有关4.0 CLR看到这个帖子:
的 http://blogs.msdn.com/b/rmbyers/archive/2008/10/27/icordebug-re -architecture-在CLR-4-0.aspx
For 4.0 CLR see this post: http://blogs.msdn.com/b/rmbyers/archive/2008/10/27/icordebug-re-architecture-in-clr-4-0.aspx
这篇关于生成/创建mdump文件在我的应用程序的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!