Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1021589
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T11:19:59+00:00 2026-05-16T11:19:59+00:00

I have a .NET application that makes calls to a native Win32 DLL using

  • 0

I have a .NET application that makes calls to a native Win32 DLL using interop services. When I run this program, it will crash somewhere inside the DLL. However, I have been unable to get any stack dump information.

When I run in the Visual Studio debugger, the debugger exits when the crash happens. I get the “Blah-blah-app has stopped working. Windows is checking for a solution to the problem…”. If I click the Debug button that appears, I get an error message saying that the process is already open in a debugger, but the debugger from which I launched the app is not functional.

I have tried to enable local crash dumps, following the instructions here: Collecting User-Mode Dumps. However, no crash dump is generated, and I notice that the page says “Applications that do their own custom crash reporting, including .NET applications, are not supported by this feature.”

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T11:20:00+00:00Added an answer on May 16, 2026 at 11:20 am

    It sounds like you are using managed debugging which is the default setting for managed projects. If you’re having a crash in a native DLL you’ll need to enable mixed mode debugging to get the events and stacks you’re looking for.

    • Right Click on the project and Select Properties
    • Go to the Debug Tab
    • Check the “Enable Unmanaged Debugging” checkbox

    Repeat your scenario.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.