Asking for help trying to debug MS's weston repo

Hi everyone, thanks a lot for the great project & sorry for bothering. This isn't really a bug per-se but more of a a question.

I'm currently trying to rebase microsoft's weston-mirror over this repo because I'd like the RAIL features, and considering the state of their repo, I sadly don't believe that MS will ever get back to upstreaming it. I know this is very naïve, considering it's my first introduction to the internals of weston, and it already looks a bit daunting. (If you're interested and FTR, you can have a look at my progress over at https://github.com/gpotter2/weston/. Also: I know that the mono-commit is bad... but it would have been honnestly 20 times the work to rebase this thing commit by commit.)

So far I have managed to rebase their patches & have the whole thing build properly (ugh that's already days of rebasing...). I'm at the point where it segfaults (expected..) but I'm honnestly a bit lost on how exactly one is supposed to gdb-attach to the various parts of weston. Most notably, from what I understand running ./weston spawns itself several processes, and the 'shells'. Is there a way to launch those separately in order to be able to, say, gdb attach to only the shell? More generally, is there doc on how to configure build for debugging purposes, stuff like that?

Sorry if this is a bit random. (Btw if anyone's interested in helping me getting this thing to work, I'd be super grateful).

Happy new year !