I've built an application - it works on my development server, and the development test device paired with it.
I've then published the application to test on another set of virtual machines with more diversity in the Operating Systems, and the application only works on one device - I have no idea why.
0:000> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3015
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 6960
Key : Analysis.IO.Other.Mb
Value: 8
Key : Analysis.IO.Read.Mb
Value: 3
Key : Analysis.IO.Write.Mb
Value: 350
Key : Analysis.Init.CPU.mSec
Value: 125217
Key : Analysis.Init.Elapsed.mSec
Value: 645009
Key : Analysis.Memory.CommitPeak.Mb
Value: 591
Key : Timeline.OS.Boot.DeltaSec
Value: 696125
Key : Timeline.Process.Start.DeltaSec
Value: 9
Key : WER.OS.Branch
Value: co_release
Key : WER.OS.Timestamp
Value: 2021-06-04T16:28:00Z
Key : WER.OS.Version
Value: 10.0.22000.1
Key : WER.Process.Version
Value: 3.1.0.0
FILE_IN_CAB: SecurityControlsDiagnosticToolkit.exe_230210_083112.dmp
COMMENT:
*** procdump.exe -e -ma -t -w "SecurityControlsDiagnosticToolkit.exe"
*** Process termination
NTGLOBALFLAG: 0
PROCESS_BAM_CURRENT_THROTTLED: 0
PROCESS_BAM_PREVIOUS_THROTTLED: 0
APPLICATION_VERIFIER_FLAGS: 0
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 0000000000000000
ExceptionCode: 80000003 (Break instruction exception)
ExceptionFlags: 00000000
NumberParameters: 0
FAULTING_THREAD: 00001820
PROCESS_NAME: SecurityControlsDiagnosticToolkit.exe
ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached.
EXCEPTION_CODE_STR: 80000003
STACK_TEXT:
00000061`fd4ff788 00007fff`48436cdf : 00000000`00000000 00000000`00000000 0000024b`fa7152c0 0000024b`fa716400 : ntdll!NtWaitForWorkViaWorkerFactory+0x14
00000061`fd4ff790 00007fff`46c355a0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!TppWorkerThread+0x2df
00000061`fd4ffa80 00007fff`4842485b : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x10
00000061`fd4ffab0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2b
STACK_COMMAND: ~0s; .ecxr ; kb
SYMBOL_NAME: ntdll!NtWaitForWorkViaWorkerFactory+14
MODULE_NAME: ntdll
IMAGE_NAME: ntdll.dll
FAILURE_BUCKET_ID: BREAKPOINT_80000003_ntdll.dll!NtWaitForWorkViaWorkerFactory
OS_VERSION: 10.0.22000.1
BUILDLAB_STR: co_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
IMAGE_VERSION: 6.2.22000.918
FAILURE_ID_HASH: {bb9287bd-f940-f1d0-c927-6d6da8a242a3}
Followup: MachineOwner
---------
All I can see here is that ntdll.dll is triggering a breakpoint exception. Googling that has yielded no results that help me understand what's happening here.
My application is published using .NET 6.0 as a self-contained file.
Each of the class libraries associated with it are all published using the same framework and build targets (.NET Core 6.0, Windows, 7.0)
I've tried both a x64 instance and x86 instance - both yield the same results.
My development virtual machines are:
Windows Server 2019 - 17763.3887
.NET Runtime 6.0
Desktop Runtime 6.0
Windows 10 SDK
Windows 10 - 18363.2274
.NET Runtime 6.0
Desktop Runtime 6.0
My test machines are:
(WORKING)
Windows Server 2019 - 17763.3887
C++ Redists (various)
Visual Studio Tools for Application 2017 (no idea what this provides, but its the only thing that I could see might make the application work)
(NOT WORKING)
Windows 10 - 19044.2546
.NET Runtime 6.0
Desktop Runtime 6.0
Windows 11 - 22000.1516
Visual Studio Tools for Application 2017
Windows Server 2016 - 14393.5648
C++ Redists (same as 2019 server)
Windows Server 2012R2 - 9600
.NET Runtime 6.0
Desktop Runtime 6.0
So I've tried a different combination of what I guessed might be prerequisites that the application might need to launch (even though its self-contained and huge) but still no luck, and I'm struggling to identify why the application just crashes with stuff external to my application.
I previously had a stack-overflow response, but now all I get is a breakpoint.
Related
Please forgive me for not speaking English well.
I am trying to use the redis sentinel function.
When I create a sentinel of redis-plus-plus, an exception is raised.
Exception occurs when Sentinel is created as shown in the code below.
image
Exceptions are as follows.
image
I've also asked git about the issue.
https://github.com/sewenew/redis-plus-plus/issues/342
Please help me.
Environment:
OS: windows7
Compiler: visual studio 2022 / unicode
hiredis version: master (date: 2022-2-2 2:10, commit:f8de9a4)
redis-plus-plus version: master (date: 2022-2-8 23:30, commit:244e8cb)
c++ version : 17
Octave 4.0.0 works on Windows 7 32 bit. I have just downloaded 4.4.1 and it has never worked.
Following information:
Problem signature:
Problem Event Name: APPCRASH
Application Name: octave-gui.exe
Application Version: 0.0.0.0
Application Timestamp: 00000000
Fault Module Name: Qt5Core.dll
Fault Module Version: 5.11.0.0
Fault Module Timestamp: 00000000
Exception Code: 40000015
Exception Offset: 002e8696
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 3081
Additional Information 1: d1e0
Additional Information 2: d1e00fdc0b78c108f75564157f84c2f0
Additional Information 3: f785
Additional Information 4: f7855e1e76ad3f0614cfa9b98110597e
Found a vaguely similar problem, failing to start GUI on Windows 10, applied suggested solution of setting "Disable display scaling on high DPI settings" under Compatibility tab of executable Properties.
If you download GNU octave from octave.org you'll see a list:
Windows-64 (recommended)
octave-4.4.1-w64-installer.exe (~ 238 MB) [signature]
octave-4.4.1-w64.7z (~ 267 MB) [signature]
octave-4.4.1-w64.zip (~ 481 MB) [signature]
Windows-32 (old computers)
octave-4.4.1-w32-installer.exe (~ 238 MB) [signature]
octave-4.4.1-w32.7z (~ 267 MB) [signature]
octave-4.4.1-w32.zip (~ 481 MB) [signature]
Of couse a 64bit built will NOT run on a Windoze7 32bit so you have to get octave-4.4.1-w32-installer.exe and install this
I am using Fedora and when I execute $ hackrf_info in the terminal, this is displayed:
Found HackRF board.
Board ID Number: 2 (HackRF One)
Firmware Version: 2014.08.1
Part ID Number: 0xa000cb3c 0x006c4757
Serial Number: 0x00000000 0x00000000 0x14d463dc 0x2f908de1
In the log section at the bottom in gnuradio-companion, HackRFOne is not displaying after debugging as an execute device.
Is there a problem with VID and PID of new versions and old hardware versions — for example statically hard-coded numbers in gnuradio-companion? D
I see this device:
Bus 002 Device 021: ID 1d50:6089 OpenMoko, Inc.
Where is the problem?
In the source code for GNU-Radio Companion, in which file/files can I edit information for detecting HackRFOne hardware?
Sorry, it's ok, I make upgrade from Fedora 20 to Fedora 21 and it's fine!
I'm opening the default project for Windows Phone 8 using VS 2012 Professional and WP8 SDK, and am trying to configure the Windows Phone 8 WVGA 512 (default) emulator.
Using build and deploy both work. Build and deploy are both checked in the build settings for all build types. The output gives me this:
Deploy started: Project: ABCD, Configuration: Debug x86
Deploying C:\Users\Guy\My Projects\ABCD\ABCD\bin\WindowsPhone\x86\Debug\ABCD_Debug_x86.xap...
Connecting to Emulator WVGA 512MB...
Installing the application...
Deployment of C:\Users\Guy\My Projects\ABCD\ABCD\bin\WindowsPhone\x86\Debug\ABCD_Debug_x86.xap succeeded.
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========
However if I try to open the Simulation Dashboard to change any settings (Lock Screen -> Unlocked or "Enable Network Simulation", Visual Studio returns the error:
Connection to Windows Phone device or emulator failed.
How do I fix this issue? I have no headway on this problem because there's nothing from Google or stackoverflow, and I've tried a ton of things related to this problem (mainly the fixes for the infamous Could Not Debug Application error.)
Thanks for the help.
I have very similar problem, but in my case the simulation does not work on actual device (it used to, but now suddenly it doesn't). It does work with emulator. Deploying and debugging works fine on both.
This would suggest that it might be more general problem. Not tied to target device type in particular.
Using MonoDroid 4.0.6 and MonoDevelop, any attempt to run in an emulator fails with this error listed below:
The minSdkVersion matches the emulator's SDK version. All AVDs were created by the MonoDroid isntaller.
Detecting package list location
Getting package list from device
Installing shared runtime package on device
1849 KB/s (25866362 bytes in 13.657s)
pkg: /data/local/tmp/Mono.Android.DebugRuntime-debug.apk
Success
Installing the platform framework
1565 KB/s (16530851 bytes in 10.310s)
pkg: /data/local/tmp/Mono.Android.Platform.apk
Failure [INSTALL_FAILED_OLDER_SDK]
Failed to install the platform framework
I solved this in 2 ways.
1) In the manifest the minSdkVersion should match or be lower than the emulator
2) (what tripped me up) The Mono DLLs References of the project should be set to the Android version too.
Both are needed. I come from a Java Android background so never thought to change anything but the manifest.