如何让Delphi调试器可视化工具拦截TIntTime类型函数返回值？

Got it, let's break down why your visualizer works for variables but not function return values like GetiTime(), and how to fix it.

First, the core issue here is almost certainly how your debugger handles type information for function return values vs. named variables. When you define TIntTime = type integer, this is a distinct type alias in Pascal terms, but under the hood it’s still an integer. Debuggers often preserve the TIntTime type name for named variables (locals, globals, class fields) because debug symbols explicitly tie that variable to the alias. But for function return values? The debugger might just expose the underlying integer type instead of the TIntTime alias—especially if the compiler doesn’t embed the alias metadata in the debug info for return values.

Here are actionable steps to fix this:

• Adjust your visualizer's type matching rules
  Most debugger visualizer frameworks (like Delphi’s .dbgvis system) let you match types in multiple ways. Right now, you’re probably only matching the exact type name TIntTime. Add a secondary rule that matches the underlying integer type, but with a condition to target only function return values that should be TIntTime. For example, if your visualizer uses XML-based configs, you might add something like:

  <Type Name="integer">
    <DisplayString Condition="IsFunctionReturnValue and GetFunctionReturnType()='TIntTime'">
      {FormatTime('hh:nn:ss', Value)}
    </DisplayString>
  </Type>
  

  The exact condition syntax depends on your visualizer’s framework, but the idea is to check if the integer value is a function return, and that the function’s declared return type is TIntTime.

• Verify debug symbol metadata
  Double-check that your compiler is emitting full debug info that includes type aliases for function return types. For Pascal/Delphi, make sure you have "Debug information" set to "Full" in your project options—sometimes partial debug info skips alias metadata for return values. You can use a debug symbol viewer (like Delphi’s tdump tool) to inspect the function’s return type info and confirm if TIntTime is present or if it’s just listed as integer.

• Target specific functions directly
  If conditional type matching isn’t feasible, you can add explicit rules for functions that return TIntTime. For example, if your visualizer lets you match monitored expressions, add a rule that triggers when the watched expression is GetiTime() (or any other TIntTime-returning function) and applies the HH:MM:SS formatting directly to the integer result.

• Check your visualizer's interception scope
  Some visualizers are configured to only intercept variables, not transient values like function return results. Make sure your tool is set to process all expression results in the watch window, not just named variables. If your visualizer uses a plugin API, check if you need to register handlers for function return value events specifically.

Once you adjust the type matching to account for how the debugger exposes function return types, your GetiTime() watch should show 08:20:00 instead of 30000 just like your variables do.

内容的提问来源于stack exchange，提问作者Jan Lauridsen