15:43:11drmeisterborodust: Interesting - it's bizarre that it can crash libclang when it must be compiled by clang.
15:48:37borodustit's not too weird - too many variables around manually processing stuff through libclang
15:48:59borodustcompared to stuff generated by build system
15:49:51borodusti'll try compilation database thing - maybe that will simplify process and get rid of most errors
15:51:28borodustbut ofc it shouldn't crash anyway - i might have hit some super edgy case
15:52:07borodustor you know, it's C/C++, maybe be i shove into it some poopointer
16:09:44drmeisterOh - I thought you were using the compilation database. I always use the compilation database - I used to run into trouble when I didn't.
16:09:54drmeisterBut that was back in the llvm3.x days.
16:16:10borodusti actually didn't know that thing existed, until we shared the notes
16:17:21borodustit works without it for most project, but huge and complex projects like libtorch is kinda tricky to get parsed correctly while manually feeding things into libclang
16:18:12borodustgonna try using compilation db approach later today and see if it makes a difference