T
tbergman
Guest
Hi Ken, This seems to work unless I have a “BLOCK-LEVEL ON ERROR UNDO, THROW.” statement in the called program. Here’s what gets written to the log when I run a program that generates an error. Note the stack trace doesn’t have anything in it. Even with –errorstack there is no trace information. Removal of the BLOCK-LEVEL statement allows it to work properly. [16/07/11@16:11:31.058-0400] P-010364 T-010344 1 4GL -- Logging level set to = 2 [16/07/11@16:11:31.058-0400] P-010364 T-010344 1 4GL -- Log entry types activated: 4GLMessages:4 [16/07/11@16:11:31.110-0400] P-010364 T-010344 1 4GL -- ** Invalid character in numeric input a. (76) [16/07/11@16:11:31.110-0400] P-010364 T-010344 1 4GL -- ** ABL Debug-Alert Stack Trace ** The startup command is _progres -b -debugalert -p testmessage.p -logentrytypes 4GLMessages:4 -clientlog foo.txt –errorstack Here’s the log without the BLOCK-LEVEL [16/07/11@16:23:58.636-0400] P-008856 T-003812 1 4GL -- Logging level set to = 2 [16/07/11@16:23:58.636-0400] P-008856 T-003812 1 4GL -- Log entry types activated: 4GLMessages:4 [16/07/11@16:23:58.706-0400] P-008856 T-003812 1 4GL -- ** Invalid character in numeric input a. (76) [16/07/11@16:23:58.706-0400] P-008856 T-003812 1 4GL -- ** ABL Debug-Alert Stack Trace ** [16/07/11@16:23:58.706-0400] P-008856 T-003812 1 4GL -- --> foo testmessage.p at line 31 (.\testmessage.r) [16/07/11@16:23:58.706-0400] P-008856 T-003812 1 4GL -- testmessage.p at line 28 (.\testmessage.r) Thanks
Continue reading...
Continue reading...