Windows error 0x000002B8, 696

Detailed Error Information

DBG_CONTROL_BREAK[1]

MessageDebugger received control break.
Declared inwinerror.h

This appears to be a raw Win32 error. More information may be available in error 0x800702B8.

HRESULT analysis: flags: none; facility: 0 (FACILITY_NULL); error: 696 (more)

Questions

2votes
0answers

Linking in .rodata and .debug_frame using arm-none-eabi-gcc

I am trying to link my .o files to generate the ELF to be run on an ARM M0+ bare metal. I am using arm-none-eabi-gcc. If I just have my C file (s) written it links fine and I can run it no problem. (For this I am providing the [...] read more
c
arm
bare-metal
0votes
1answer

obexftp -l fails, return code 81

I am currently attempting to use obex tools to browse (and later mount) the file system of an Android device (7.1.1). When I try to list using obexftp -l, it simply returns nothing. I have tried almost every possible combination of file parameters after -l, but still get the same [...] read more
android
linux
bluetooth
obex
obexftp
-1votes
1answer

CUDA: Cuda memory accessing different than OpenCL? What is causing this illegal memory access?

So I wrote a Cuda version of an OpenCL program I wrote. The OpenCL versions works, meanwhile the Cuda version doesn't. Now converting OpenCL code to Cuda code isn't 1-to-1, but I'm confused as to why the cuda version wouldn't work after all I did base my code around an [...] read more
c++
memory
cuda
gpgpu
memory-access

Comments

Leave a comment

(plain text only)

Sources

  1. winerror.h from Windows SDK 10.0.14393.0
  2. https://msdn.microsoft.com/en-us/library/cc231198.aspx

User contributions licensed under CC BY-SA 3.0