Chromium Code Reviews| Index: src/trusted/service_runtime/nacl_oop_debugger_hooks.c |
| =================================================================== |
| --- src/trusted/service_runtime/nacl_oop_debugger_hooks.c (revision 0) |
| +++ src/trusted/service_runtime/nacl_oop_debugger_hooks.c (revision 0) |
| @@ -0,0 +1,120 @@ |
| +/* Copyright (c) 2011 The Native Client Authors. All rights reserved. |
| + * Use of this source code is governed by a BSD-style license that can be |
| + * found in the LICENSE file. |
| + */ |
| + |
| +#include "native_client/src/trusted/service_runtime/nacl_oop_debugger_hooks.h" |
| +#include "native_client/src/trusted/service_runtime/sel_ldr.h" |
| + |
| +#ifdef _WIN32 /* _WIN32 is defined on both 32-bit and 64-bit Windows */ |
|
Mark Seaborn
2011/06/13 19:40:51
Use NACL_WINDOWS instead.
garianov1
2011/06/13 20:09:10
Done.
|
| +/* Note: this function does not do anything if program |
| + * is not running under debugger. |
| + * If program (sel_ldr) is running under debugger, calling this function |
| + * gives debugger a chance to modify state of the debuggee before |
| + * resuming debuggee execution. |
| + */ |
| +void SendMessageToDebuggerAndHalt(const char* fmt, ...); |
| + |
| +void NaClOopDebuggerAppCreateHook(struct NaClApp* nap) { |
| + if (NULL == nap) |
| + return; |
| + SendMessageToDebuggerAndHalt( |
| + "-event AppCreate -nap %p -mem_start %p -user_entry_pt %p " |
| + "-initial_entry_pt %p", |
| + nap, |
| + (void*)nap->mem_start, |
|
Mark Seaborn
2011/06/13 19:40:51
Style in this component is "(void *) foo".
garianov1
2011/06/13 20:09:10
Done.
|
| + (void*)nap->user_entry_pt, |
| + (void*)nap->initial_entry_pt); |
| +} |
| + |
| +void NaClOopDebuggerThreadCreateHook(struct NaClAppThread* natp) { |
| + SendMessageToDebuggerAndHalt("-event ThreadCreate -natp %p", natp); |
| +} |
| + |
| +void NaClOopDebuggerThreadExitHook(struct NaClAppThread* natp, int exit_code) { |
| + SendMessageToDebuggerAndHalt("-event ThreadExit -natp %p -exit_code %d", |
| + natp, |
| + exit_code); |
| +} |
| + |
| +void NaClOopDebuggerAppExitHook(int exit_code) { |
| + SendMessageToDebuggerAndHalt("-event AppExit -exit_code %d", exit_code); |
| +} |
| + |
| +#else |
| +/* placeholders for OOP debugger hooks on other platforms */ |
| +void NaClOopDebuggerAppCreateHook(struct NaClApp* nap) { |
| + UNREFERENCED_PARAMETER(nap); |
| +} |
| + |
| +void NaClOopDebuggerThreadCreateHook(struct NaClAppThread* natp, |
| + int exit_code) { |
| + UNREFERENCED_PARAMETER(natp); |
| + UNREFERENCED_PARAMETER(exit_code); |
| +} |
| +void NaClOopDebuggerThreadExitHook(struct NaClAppThread* natp, |
| + int exit_code) { |
| + UNREFERENCED_PARAMETER(natp); |
| + UNREFERENCED_PARAMETER(exit_code); |
| +} |
| + |
| +void NaClOopDebuggerAppExitHook(int exit_code) { |
| +} |
| +#endif |
| + |
| +#ifdef _WIN32 /* _WIN32 is defined on both 32-bit and 64-bit Windows */ |
| +void SendMessageToDebuggerAndHalt(const char* fmt, ...) { |
| +#define kVarMsgSize 2048 |
|
Mark Seaborn
2011/06/13 19:40:51
Use "const int" (local) or "static const int" (glo
garianov1
2011/06/13 20:09:10
Unfortunately, if I use 'const int', the following
|
| + /* Determines whether the calling process is being debugged by a debugger. |
|
Mark Seaborn
2011/06/13 19:40:51
Style here is
/*
* comment...
*/
garianov1
2011/06/13 20:09:10
Done.
|
| + * IsDebuggerPresent() is a member of Windows Debugging API: |
| + * http://msdn.microsoft.com/en-us/library/ms680345%28v=VS.85%29.aspx |
| + */ |
| + if (IsDebuggerPresent()) { |
| + /* Prefix has GUID string specific to our OOP debugger, so that it |
| + * can differentiate it from other uses of 'OutputDebugString'. |
| + */ |
| + char prefix[] = "{7AA7C9CF-89EC-4ed3-8DAD-6DC84302AB11} -version 1 "; |
| + char msg[sizeof(prefix) + kVarMsgSize]; |
| + char* post_pref_msg = msg + sizeof(prefix) - 1; |
|
Mark Seaborn
2011/06/13 19:40:51
Style here is "char *foo".
garianov1
2011/06/13 20:09:10
Done.
|
| + signed int res = 0; |
| + va_list marker; |
| + |
| + strcpy(msg, prefix); |
| + va_start(marker, fmt); |
| + res = _vsnprintf_s(post_pref_msg, kVarMsgSize, _TRUNCATE, fmt, marker); |
| + if (-1 != res) { |
| + /* Sends a string to the debugger by raising OUTPUT_DEBUG_STRING_EVENT. |
| + * OutputDebugString() is a member of Windows Debugging API: |
| + * http://msdn.microsoft.com/en-us/library/aa363362%28v=VS.85%29.aspx |
| + * |
| + * It's conceptually eqvivalent to: |
| + * ::RaiseException(MY_OWN_EXCEPTION_CODE, 0, 1, &msg); |
| + * The difference is, raising MY_OWN_EXCEPTION_CODE can cause program |
| + * to crash (if there's no VEH handler and no debugger; or can cause |
| + * debugger to stop program (if debugger does not know about |
| + * MY_OWN_EXCEPTION_CODE). |
| + * |
| + * On the contrary, using OutputDebugString() is safe, cc from MSDN page: |
| + * "If the application has no debugger and the system debugger is not |
| + * active, OutputDebugString does nothing." |
| + */ |
| + OutputDebugStringA(msg); |
| + } |
| + } |
| +#undef kVarMsgSize |
| +} |
| +/* Example of captured sel_ldr -> debugger messages: |
| + |
| +11.62454796 [6060] {7AA7C9CF-89EC-4ed3-8DAD-6DC84302AB11} -version 1 \ |
| + -event AppCreate -nap 00000000001CD3F0 -mem_start 0000000C00000000 \ |
| + -user_entry_pt 0000000000020080 -initial_entry_pt 0000000008000080 |
| +11.62480354 [6060] {7AA7C9CF-89EC-4ed3-8DAD-6DC84302AB11} -version 1 \ |
| + -event ThreadCreate -natp 0000000002304C50 |
| +... |
| +23.96814728 [6060] {7AA7C9CF-89EC-4ed3-8DAD-6DC84302AB11} -version 1 \ |
| + -event ThreadExit -natp 0000000002304C50 -exit_code 1 |
| +23.96838570 [6060] {7AA7C9CF-89EC-4ed3-8DAD-6DC84302AB11} -version 1 \ |
| + -event AppExit -exit_code 1 |
| +*/ |
| +#endif |
| + |