How to Find Out If "Debug Mode" Is Enabled

How to find out if debug mode is enabled

I found it out myself now:

boolean isDebug = java.lang.management.ManagementFactory.getRuntimeMXBean().
    getInputArguments().toString().indexOf("jdwp") >= 0;

This will check if the Java Debug Wire Protocol agent is used.

windows 10 check if debugging mode is enabled?

This is how you check if debugging mode is enabled:

1. Type regedit into search bar.
2. Go to this key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
3. Double-click this value: SystemStartOptions
4. If debugging mode is enabled it should include the port and say "DEBUG": FLIGHTSIGNING NOEXECUTE=OPTIN DEBUGPORT=1394 FVEBOOT=2670592 NOVGA DEBUG

If it's not enabled it just says "NODEBUG": FLIGHTSIGNING NOEXECUTE=OPTIN NODEBUG FVEBOOT=2670592 NOVGA

In this picture it shows it is enabled by having the port and "DEBUG" listed:

Check if Debug is enabled in Visual C#

In the code:

#if DEBUG
// do something
#endif

How do I detect if I am in release or debug mode?

The simplest, and best long-term solution, is to use BuildConfig.DEBUG. This is a boolean value that will be true for a debug build, false otherwise:

if (BuildConfig.DEBUG) {
  // do something for a debug build
}

There have been reports that this value is not 100% reliable from Eclipse-based builds, though I personally have not encountered a problem, so I cannot say how much of an issue it really is.

If you are using Android Studio, or if you are using Gradle from the command line, you can add your own stuff to BuildConfig or otherwise tweak the debug and release build types to help distinguish these situations at runtime.

The solution from Illegal Argument is based on the value of the android:debuggable flag in the manifest. If that is how you wish to distinguish a "debug" build from a "release" build, then by definition, that's the best solution. However, bear in mind that going forward, the debuggable flag is really an independent concept from what Gradle/Android Studio consider a "debug" build to be. Any build type can elect to set the debuggable flag to whatever value that makes sense for that developer and for that build type.

How do I check if Debug is enabled in web.config

Use:

HttpContext.Current.IsDebuggingEnabled

This property actually looks at the web.config configuration setting. If you look at it using Reflector you will find that it gets the actual ConfigurationSection object using some internal classes.

How can I check if debug information is enabled in angular?

The debugInfoEnabled function is a setter/getter. It can be checked in a config block.

app.config(function ($compileProvider) {
    var debugEnabled = $compileProvider.debugInfoEnabled();
    console.log("debugInfoEnabled=", debugEnabled);
});

See the source code.

How to detect if debugging

HttpContext is another HttpContext than you were used to since you are now using ASP.NET Core. That property can't be found in the ASP.NET Core variant. An explanation of the differences is given by poke.

I would use Debugger.IsAttached, which not only checks if debugging is enabled, but also actively being debugged.

How can I check if a Flutter application is running in debug?

While this works, using constants kReleaseMode or kDebugMode is preferable. See Rémi's answer below for a full explanation, which should probably be the accepted question.

---

The easiest way is to use assert as it only runs in debug mode.

Here's an example from Flutter's Navigator source code:

assert(() {
  if (navigator == null && !nullOk) {
    throw new FlutterError(
      'Navigator operation requested with a context that does not include a Navigator.\n'
      'The context used to push or pop routes from the Navigator must be that of a '
      'widget that is a descendant of a Navigator widget.'
    );
  }
  return true;
}());

Note in particular the () at the end of the call - assert can only operate on a Boolean, so just passing in a function doesn't work.

How to determine whether code is running in DEBUG / RELEASE build?

Check your project's build settings under 'Apple LLVM - Preprocessing', 'Preprocessor Macros' for debug to ensure that DEBUG is being set - do this by selecting the project and clicking on the build settings tab. Search for DEBUG and look to see if indeed DEBUG is being set.

Pay attention though. You may see DEBUG changed to another variable name such as DEBUG_MODE.

then conditionally code for DEBUG in your source files

#ifdef DEBUG

// Something to log your sensitive data here

#else

// 

#endif

---

Related Topics