Annoyance - Contractor UK Bulletin Board

Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

RSoles replied

23 January 2016, 11:28
Ah yes, I remember a card which worked perfectly on an extender, back in the rack, dead as a dead thing.
Leave a comment:
NotAllThere replied

23 January 2016, 10:34
What runs perfectly (and debuggerable) in foreground will fail in background.
Leave a comment:
NickFitz replied

23 January 2016, 09:09
Originally posted by d000hg View Post

When the cause of the crash in your application turns out to be the debugging/tracing code you added to see what was going on.

Or, indeed, the other way round: you add the debug/trace code, it stops crashing. Remove it, it crashes again
Leave a comment:
d000hg started a topic Annoyance

22 January 2016, 19:30
Annoyance

When the cause of the crash in your application turns out to be the debugging/tracing code you added to see what was going on.
Tags: None

Working...

X