Problems using error object

[Cliff Wiernik]

Unfortunately procname(2), procline(2) point to the calling function 2 levels up.

bExtract:= {|a,b,o,x| S_Extract(Getlist,oV)} // Extract configured data

Which is the code block activated by the DCPUSHUBUTTON.

[Auge_Ohr]

Code: Select all

  BEGIN SEQUENCE
  
  DO WHILE !EOF()
    SOME CODE
    SKIP
  ENDDO

are you using Alaska DBE or ADS or other ?
what does it show when NOT using your own Errorblock -> Original ?

[reganc]

I have error handling where I have to call a function, eg. my_error(), instead of puttiing just 'break(oError)' into the codeblock.

The function reads the callstack text and puts it into the oError:cargo variable and then does the 'break(oError)' call. That way the callstack is being read in the thread the error occurred in instead of in the error handling thread. And then the value of oError:cargo variable can be read to get the callstack text in the RECOVER..USING bit.

[Cliff Wiernik]

Do you have a small code sample to illustrate.

Maybe Roger can provide a code sample also.

[Cliff Wiernik]

Using ADS and without the error handler, I get the normal runtime error.

[Cliff Wiernik]

Thanks, all for the help, especially Regan.

When I created a function and posted procname(2),procline(2) to cargo, prior to the break(oError), I got the line needed. Now I can make my dumb custom error handling better.

Cliff