Re: Panic on new system

I should tell the mailing list what caused Lua to panic, so a future person will have a clue.

Somebody mangled our Makefiles so that a cpp file wasn't recompiled when a header file changed. It had a different memory map than all the other .o files, so naturally there were problems.

The problem could have been identified by running the program under Valgrind. If someone else experiences Lua panics, I recommend they run Valgrind first thing.

Thanks for your help.

On Fri, May 24, 2019 at 10:18 PM Rick Hedin <cubsno1@gmail.com> wrote:

Hmm. I'm not sure what I should do with the ldd output. Make sure it's the same on both systems?

I'd like to build the program on the target system. It's not the way we've been doing things at work. But it seems desirable. I'll see whether my coworkers will go for it.

Regards, Rick

On Fri, May 24, 2019 at 9:26 PM Sean Conner <sean@conman.org> wrote:
It was thus said that the Great Rick Hedin once stated:
> Hi, Sean.
>
> Both systems report the same version.
>
> cdx-dev:/home/rhedin/ctrace> lua -v
> Lua 5.1.4 Copyright (C) 1994-2008 Lua.org, PUC-Rio
>
> The ctrace I downloaded was this one.
>
> http://webserver2.tecgraf.puc-rio.br/~lhf/ftp/lua/5.1/ctrace.tar.gz
>
> Note the 5.1 in the path.
>
> I wondered whether the version of the operating system could matter. On
> the development machine:
>
> cdx-dev:/home/rhedin/ctrace> cat /etc/redhat-release
> Red Hat Enterprise Linux Server release 6.10 (Santiago)
>
> On the QA machine, it says it's 6.7. So they're not the same. Important?

I'm not sure. I've always compiled the stuff on the target machine---even
at work we have build servers that match what we have in QA, staging and
production. One thing to check on each machine would be:

GenericUnixPrompt% ldd ctrace.so # or whatever the Lua module name is

An example:

[spc]lucy:~/projects/lua-conmanorg/lib>ldd syslog.so
libc.so.6 => /lib/tls/libc.so.6 (0x002e6000)
/lib/ld-linux.so.2 (0x00b76000)

But if at all possible, can you compile on the QA machine and test it? If
it's still a problem, then ... um ... not sure where to go from here.

-spc