Skip to main content

ProcScript Tracing Messages

  • October 17, 2019
  • 7 replies
  • 0 views

Found this line in the UnifAce library

"When the Debugger tracing setting is set to value 16 (trace all activate information), the $procerrorcontext information for the some errors appears in the message frame."

Where to set this value?

$ioprint does have 16, but this is a another story

$proc_tracing is a bool flag

Maybe a undocumented function like $traceprint? grinning  🙂

Ingo


7 replies

Gianni Sandigliano
Forum|alt.badge.img

Found this line in the UnifAce library

"When the Debugger tracing setting is set to value 16 (trace all activate information), the $procerrorcontext information for the some errors appears in the message frame."

Where to set this value?

$ioprint does have 16, but this is a another story

$proc_tracing is a bool flag

Maybe a undocumented function like $traceprint? grinning  🙂

Ingo


Hi Ingo,

in the earliest Uniface tracing I was aware of (U7 times) I was using in my assignment files lines like:

; Specify which informations should be traced
$trc_levels = 9A-Za-z6c5s0R5t0z0N
; Specify additional informations to be traced
$trc_info = cat,lvl,dtt

AFAIAK informations about those settings could still be reached at: http://www.march-hare.com/puuu/doc/traceuuu.html

Hope it could be useful...

Gianni



  • October 18, 2019

Found this line in the UnifAce library

"When the Debugger tracing setting is set to value 16 (trace all activate information), the $procerrorcontext information for the some errors appears in the message frame."

Where to set this value?

$ioprint does have 16, but this is a another story

$proc_tracing is a bool flag

Maybe a undocumented function like $traceprint? grinning  🙂

Ingo


Hi Gianni

Maybe but I don't believe so 🙂
Looks more like $traceprint=16
Could not verfiy, as I'm not in my office

Ingo




  • Rocketeer
  • October 18, 2019

Hi Gianni

Maybe but I don't believe so 🙂
Looks more like $traceprint=16
Could not verfiy, as I'm not in my office

Ingo



Just do a quick web search:

http://www.march-hare.com/puuu/undoc/traceprint.html

😉


  • October 18, 2019

Hi Gianni

Maybe but I don't believe so 🙂
Looks more like $traceprint=16
Could not verfiy, as I'm not in my office

Ingo



Hi Daniel

My question was a simple "catch question" grins 

Why is there no reference no this web site in your documentation

Testing and Debugging > Debugging Uniface Applications > ProcScript Profiling and Tracing > ProcScript Tracing Messages

Ingo


  • Rocketeer
  • October 18, 2019

Hi Gianni

Maybe but I don't believe so 🙂
Looks more like $traceprint=16
Could not verfiy, as I'm not in my office

Ingo



The clue is in the title of the linked page:

> Uniface Underground -> Undocumented.Features.Only.

😉


Iain Sharp
Forum|alt.badge.img+5
  • Inspiring
  • October 18, 2019

Hi Gianni

Maybe but I don't believe so 🙂
Looks more like $traceprint=16
Could not verfiy, as I'm not in my office

Ingo



So, to be clear, the debugger tracing switch is not documented, but an action of the debugger tracing switch IS documented. Interesting. 😜


  • Rocketeer
  • October 18, 2019

Hi Gianni

Maybe but I don't believe so 🙂
Looks more like $traceprint=16
Could not verfiy, as I'm not in my office

Ingo



No, the ProcScript function $traceprint is not documented. The fact that the Debugger is using this function internally to enable some tracing is not really relevant, I would say.