#4524 Callback errors are swallowed up

obsolete: 8.5.8

Errors occurring during the script given by the -command option to geturl are not reported anywhere in the normal fashion (bgerror). I did discover they end up in the http token under "error", but the documentation doesn't describe this behaviour at all (only actual HTTP errors). Besides, that would be really, really messy to handle as obviously there's nothing in my "own" stack that knows the callback has just been evaluated and to then look for an error.


  • kjnash

    kjnash - 2012-10-30

    Duplicate of 1414262

  • Donal K. Fellows

    • status: open --> closed-duplicate

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks