I am going on a slightly different approach.
I did: #apt-get build-dep vte2.91 #apt-get source vte2.91 vte2.91, come with an example called app... modified src/app/meson.build to add: -g -O0 to cflags meson _build ninja -C _build gdb _build/src/app/vte-2.91 break 1394 p message->error -> "Failed to execute child process \342\200\234/bin/bash\342\200\235: Failed to fdwalk: Too many open files in the system" which in xterm appears as â/bin/bashâ I was asking myself if the bash part was containing all or part of \342\200\234, but I guess not... guessing this is something like open-quote, close-quote characters. Still getting difficulty to navigate through source code with gdb to pinpoint the problem. Now I am thinking that if I make the packages, then install debug symbol package(s)... it should help me.
