Hmm. I think there was a case where we were not returning in a function, and this might cause bamf to throw up. Ideally bamf should probably safeguard against invalid xid's.
Can you post the full stacktrace ?
Hmm. I think there was a case where we were not returning in a function, and this might cause bamf to throw up. Ideally bamf should probably safeguard against invalid xid's.
Can you post the full stacktrace ?