Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. Bad Bad problem

Bad Bad problem

Scheduled Pinned Locked Moved C#
helpcsharpquestionvisual-studiodebugging
3 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    Den2Fly
    wrote on last edited by
    #1

    Hello everybuddy, Listen! I have a bad bothering problem, I made a big effort to solve but no result yet. My project is going to be late and I have a short time. It is a TCP/IP multithread socket based application. At some point after event I see the result of some action ok, after some seconds following exception occures in Visual Studio .NET (while in debug mode): "An unhandled exception of type 'System.Xml.XmlException' occurred in Unknown Module. Additional information: System error." When I click "Break" it says: "There is no source code available for this location" What is XmlException ??? what the problem can be ??? I'd appreciate any help. - Den --- "Art happens when you least expect it."

    C A 2 Replies Last reply
    0
    • D Den2Fly

      Hello everybuddy, Listen! I have a bad bothering problem, I made a big effort to solve but no result yet. My project is going to be late and I have a short time. It is a TCP/IP multithread socket based application. At some point after event I see the result of some action ok, after some seconds following exception occures in Visual Studio .NET (while in debug mode): "An unhandled exception of type 'System.Xml.XmlException' occurred in Unknown Module. Additional information: System error." When I click "Break" it says: "There is no source code available for this location" What is XmlException ??? what the problem can be ??? I'd appreciate any help. - Den --- "Art happens when you least expect it."

      C Offline
      C Offline
      Christian Graus
      wrote on last edited by
      #2

      Den2Fly wrote: What is XmlException ??? An exception that occurs during the handling of XML. Does your code use XML anywhere ? Den2Fly wrote: "There is no source code available for this location" That means that where it blew up is within the framework, but you should still be able to use the stack trace to work out where your code called the method that blew up, then look at what you passed in, which is bound to be where the problem lies. I hope. Christian I have several lifelong friends that are New Yorkers but I have always gravitated toward the weirdo's. - Richard Stringer

      1 Reply Last reply
      0
      • D Den2Fly

        Hello everybuddy, Listen! I have a bad bothering problem, I made a big effort to solve but no result yet. My project is going to be late and I have a short time. It is a TCP/IP multithread socket based application. At some point after event I see the result of some action ok, after some seconds following exception occures in Visual Studio .NET (while in debug mode): "An unhandled exception of type 'System.Xml.XmlException' occurred in Unknown Module. Additional information: System error." When I click "Break" it says: "There is no source code available for this location" What is XmlException ??? what the problem can be ??? I'd appreciate any help. - Den --- "Art happens when you least expect it."

        A Offline
        A Offline
        Ami Bar
        wrote on last edited by
        #3

        I had one of these. Try to set the CLR exception to break into the debugger. In the Visual Studio .NET when a solution is open open the Debug menu and choose Exceptions. In the dialog choose the 'Common Language Runtime Exceptions'. Then change the radio button below of the 'When the exception is thrown:' to 'Break into the debugger'. This way as soon as the exception is thrown you break into the debugger and not in the place it is caught. P.S. You can restore the exceptions to their default setting by pressing the 'Clear All' button. Good luck, Ami

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups