Summary

store call-trace in error condition object

Metadata

• Id: 544e6d74ed5c7b0e47f0b0eaf92e11b4563633a2
• Trac id: 348
• Type: defect
• Reporter: felix
• Owner: felix
• Cc:
• Status: closed
• Component: core libraries
• Estimated difficulty:
• Resolution: fixed
• Priority: minor
• Milestone: 4.9.0
• Version: 4.5.x
• Changetime: 2012-09-24 21:47:48 UTC
• Created: 2010-08-22 12:06:00 UTC
• Keywords: conditions call-trace

Description

When printing an error-message, the call-trace at the point of error should be shown, because otherwise trace-info between condition-raising and the actual extraction+printing of the call-trace will also show up in the trace.

(suggested by Christian Kellermann)

Changes and comments

[2010-08-24 12:13:36 UTC] felix changed milestone from 4.6.0 to 4.7.0

[2010-09-14 15:28:47 UTC] felix changed status from new to closed

[2010-09-14 15:28:47 UTC] felix set resolution to fixed

[2010-09-14 15:28:47 UTC] felix wrote:

Done in csi now (4.6.1). I currently don't know if that is sufficient, please give it a try.

[2011-06-01 09:00:41 UTC] felix changed milestone from 4.7.0 to 4.8.0

[2011-06-01 09:00:41 UTC] felix wrote:

Milestone 4.7.0 deleted

[2012-09-24 21:47:48 UTC] felix changed milestone from 4.8.0 to 4.9.0

[2012-09-24 21:47:48 UTC] felix wrote:

Milestone 4.8.0 deleted