MirrorSave
/
nodemcu-firmware
mirror of https://github.com/nodemcu/nodemcu-firmware.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix build problem with luac.cross when DEVELOPMENT_USE_GDB is used (#2569)

This commit is contained in:
galjonsfigur 2018-11-23 19:02:07 +01:00 committed by Terry Ellison
parent bb9a5977d3
commit d5aca39f48
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
app/lua/lauxlib.c
View File

@ -958,12 +958,12 @@ LUALIB_API void luaL_assertfail(const char *file, int line, const char *message)
#endif #endif
} }
#ifdef DEVELOPMENT_USE_GDB #if defined(DEVELOPMENT_USE_GDB) && !defined(LUA_CROSS_COMPILER)
/* /*
* This is a simple stub used by lua_assert() if DEVELOPMENT_USE_GDB is defined. * This is a simple stub used by lua_assert() if DEVELOPMENT_USE_GDB is defined.
* Instead of crashing out with an assert error, this hook starts the GDB remote * Instead of crashing out with an assert error, this hook starts the GDB remote
* stub if not already running and then issues a break. The rationale here is * stub if not already running and then issues a break. The rationale here is
* that when testing the developer migght be using screen/PuTTY to work ineractively * that when testing the developer might be using screen/PuTTY to work interactively
* with the Lua Interpreter via UART0. However if an assert triggers, then there * with the Lua Interpreter via UART0. However if an assert triggers, then there
* is the option to exit the interactive session and start the Xtensa remote GDB * is the option to exit the interactive session and start the Xtensa remote GDB
* which will then sync up with the remote GDB client to allow forensics of the error. * which will then sync up with the remote GDB client to allow forensics of the error.