• 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!

Annoyance

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    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.
    Originally posted by MaryPoppins
    I'd still not breastfeed a nazi
    Originally posted by vetran
    Urine is quite nourishing

    #2
    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

    Comment


      #3
      What runs perfectly (and debuggerable) in foreground will fail in background.
      Down with racism. Long live miscegenation!

      Comment


        #4
        Ah yes, I remember a card which worked perfectly on an extender, back in the rack, dead as a dead thing.

        Comment

        Working...
        X