I actually, really think that this is a so-called "troll" letter.
My arguments are such:
1. The letter seem to be copy-pasted.
2. The sender did not mention any specific problem. He mentioned that
"something" is wrong with "something".
3. No minimal reproducable testcase. It is a sign that the sender do not
wish to spend any time on the problem(if such exists). He just wants US to
spend OUR time.
4. He made some claims that is wrong. Such that gdb can not debug an
executable. He provokes a "troll" reaction.
I urge you to ignore the e-mail chain of this sender.
сб, 23 мая 2020 г. в 08:56, Open Skies <alexjiverson@xxxxxxxxx>:
How does it crash? What error message or error code does it produce? What
did you expect to happen versus what actually happened? How do you know it
crashed at coroutine.resume()?
On Fri, May 22, 2020 at 10:52 PM Javier Guerra Giraldez <
javier@xxxxxxxxxxx> wrote:
On Fri, 22 May 2020 at 15:03, Andriy Grytsenko
<dmarc-noreply@xxxxxxxxxxxxx> wrote:
GUI back-end. The problem is that /usr/bin/lua crashes on execution of Lua
Hello!
We are using OpenWRT based solution and use luajit 2.1.0-beta2 for Luci
script at coroutine.resume() and I found no way to add any debug code as
everything in LuaJIT seems to be written in some kind of assembler code.
Using gdb or valgrind isn't possible because it is an device with 32 MB
memory and 8 MB flash. Could you give any hint if I can do anything? Thanks
in advance.
my 2¢:
- try to get _minimal_ reproducing testcase. Sometimes this is really
difficult, but is really a huge help.
- once you can easily and reliably reproduce the problem, try it on
emulated hardware, not only that allows other people to help you, it
might allow you to run a debugger.
--
Javier
