Hi Ying, If you manage to get the debugger to work nicely with VScode, could you share the instructions on how to do set this up? I usually just use gdb, but that can be a bit crude, would love to use a visual debugger sometimes.
Regards, Maarten Breddels Software engineer / consultant / data scientist Python / C++ / Javascript / Jupyter www.maartenbreddels.com / vaex.io [email protected] +31 6 2464 0838 <+31+6+24640838> [image: Twitter] <https://twitter.com/maartenbreddels>[image: Github] <https://github.com/maartenbreddels>[image: LinkedIn] <https://linkedin.com/in/maartenbreddels>[image: Skype] On Thu, Feb 25, 2021 at 12:25 PM Ben Kietzman <[email protected]> wrote: > Hi Ying, > > You could also try the --gtest_break_on_failure flag (or equivalently the > GTEST_BREAK_ON_FAILURE=1 environment). > > Ben > > > On Thu, Feb 25, 2021, 05:00 Antoine Pitrou <[email protected]> wrote: > > > > > Hi Ying, > > > > Have you tried using the given test executable as a debug target? > > (something like build/debug/arrow-orc-writer.exe) > > > > Also, it has various command-line options to change behaviour and narrow > > down the tests (I suggest trying --gtest_filter=...). > > > > Regards > > > > Antoine. > > > > > > Le 25/02/2021 à 09:22, Ying Zhou a écrit : > > > Hi, > > > > > > To facilitate faster debugging I’d like to integrate make unittest > > debugging into VSCode (on Mac) so that when I run a test that might show > > some bugs breakpoints can stop the execution so that I can dig around a > > bit. Does anyone know how that can be done? I know it is a stupid > question > > but it does need to be addressed so that I can finish the ORC writer with > > visitors ASAP. > > > > > > Thanks, > > > Ying > > > > > >
