Search Issue Tracker

Fixed in 2019.1

Votes

14

Found in

5.3.0f4

Issue ID

753944

Regression

No

Assigning a custom Debug.logger.logHandler doesn't intercept thrown exceptions

Scripting

-

To reproduce:
1. Open project
2. Press play
Notice that the "Test" class intercepts Debug.Log and Debgu.LogException, but doesn't intercept the exception it throws.

Comments (3)

  1. 3675ff04054bdcda54b841861f424f5a?d=mm

    k0mbain

    Jan 19, 2018 13:15

    Present in 2017.1.2p3. It has almost 2 years. Duh!

  2. 551c57213fd89d23b2d7633b385e32e0?d=mm

    LKWD_JamesD

    May 02, 2017 09:26

    Present in 5.4.5f1.

    Is there any way to catch these?

  3. 39d80a01b98e2631b97ff9d235c1222c?d=mm

    Tinus

    May 24, 2016 16:54

    Just ran into this issue. We're trying to route all exceptions to GetSentry.com, a REST service but are having significant trouble finding the correct point to insert logging hooks. Capturing all Debug.Log callbacks can be done through multiple means, but this appears to be the only place to get exceptions.

    Except, while the LogFormat callback of the ILogHandler interface is called, the LogException callback is completely dormant.

    This is still an issue as of 5.3.5f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.