Windows error 0x00000111, 273

Detailed Error Information

RECURSIVE_NMI[1]

This is a Blue Screen of Death stop code. More information is available in the Knowledge Base article Bug Check 0x111: RECURSIVE_NMI.

HRESULT analysis[2]

This is probably not the correct interpretation of this error. The Win32 error above is more likely to indicate the actual problem.
FlagsSeveritySuccess

This code indicates success, rather than an error. This may not be the correct interpretation of this code, or possibly the program is handling errors incorrectly.

Reserved (R)false
OriginMicrosoft
NTSTATUSfalse
Reserved (X)false
FacilityCode0 (0x000)
NameFACILITY_NULL[2][3]
DescriptionThe default facility code.[2][3]
Error Code273 (0x0111)

Possible solutions

2

Use awk to get value of the parameter in the array

bash
awk
grep
journal

Using sed:

$ echo "aaa: 0x00000111 bbb: 0x00000222 ccc: 0x00000333 ddd: 0x00000444"|sed 's/.*ccc: \([^ ]*\).*/\1/g'
0x00000333

If you really want to use awk:

$ echo "aaa: 0x00000111 bbb: 0x00000222 ccc: 0x00000333 ddd: 0x00000444"|awk '/ccc:/{s=$0; gsub(".*ccc: ", "", s); gsub(" .*$", "", s); print s}'
0x00000333
answered on Stack Overflow Jun 29, 2018 by Idriss Neumann • edited Jun 29, 2018 by Idriss Neumann
2

Use awk to get value of the parameter in the array

bash
awk
grep
journal

This line will give your the value if the key is ccc:

journalctl -b|grep -oP 'ccc: \K[^ :]*'

e.g.

kent$  grep -oP 'ccc: \K[^: ]*'<<<"aaa: 0x00000111 bbb: 0x00000222 ccc: 0x00000333 ddd: adfa"
0x00000333
answered on Stack Overflow Jun 29, 2018 by Kent • edited Jun 29, 2018 by Kent
0

Use awk to get value of the parameter in the array

bash
awk
grep
journal

For provided example, could you please try following and let us know then.

echo "aaa: 123 bbb: 456 ccc: 789" | awk '{sub(/.*ccc: /,"");sub(/ .*/,"")} 1'

Or by usual loop way from awk.

echo "aaa: 123 bbb: 456 ccc: 789" | awk '{for(i=1;i<=NF;i++){if($i=="ccc:"){print $(i+1);next}}}'
answered on Stack Overflow Jun 29, 2018 by RavinderSingh13 • edited Jun 29, 2018 by RavinderSingh13
0

WTL window/form crashes after infinite message loop causes stack overflow

visual-c++
wtl

Found this, thanks to @Roman R. - in the window in question, there was no handler for the WM_COMMAND message, and in one of its base classes there was a function that generated the infinite loop by forwarding the message back to the active window. So I added this handler -

        if(uMsg == WM_COMMAND)
          return DefWindowProc(WM_COMMAND, wParam, lParam);

which seems like a good solution for me.

Thanks!

answered on Stack Overflow Oct 29, 2011 by Oleg Ivanov

Comments

Leave a comment

(plain text only)

Sources

  1. https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-code-reference2
  2. https://msdn.microsoft.com/en-us/library/cc231198.aspx
  3. winerror.h from Windows SDK 10.0.14393.0

User contributions licensed under CC BY-SA 3.0