Re: Using VSCode With gr-tutorial

[David Cherkus]

I too found a short-term workaround, but will keep that in mind when I revisit the topic, which I'm sure will be soon.

On the topic of debugging from an IDE, I found the tutorial for Eclipse and it said one could only debug standalone QA code (if I interpreted it correctly).

Doesn't the same technique used by the VS Code tutorial ( just use the debugger to launch /usr/bin/python3 with your Python script as an argument to it, then the debugger can/will hit breakpoints in the shared libs that get loaded for your implementation) work?   Or does Eclipse's debug launcher insist on only launching things you build in your project?

Overall I will be OK with just using the IDEs for code browsing and building and running gdb the old school way, from the command line, but would be better if better solutions to work from an IDE were found.

Regards,

Dave

On Tuesday, February 22, 2022, 11:11:12 AM EST, Jeff S <e070832@hotmail.com> wrote:

Dave,

I came across a situation that you described.  I had a breakpoint, and I disabled it after hitting it.  Sure enough, it brroke there again.  It seems to be hitting it from another thread.  So, check your call stack when you come across that situation and it may be that it is coming from another thread.  I'm not sure why it does it that way, maybe because all threads hit the breakpoint and VSC is just cycling through all of the breaks (?).  I haven't spent much time on investigating it because it wasn't stopping me from doing what I needed to do.

Just a thought,
Jeff

________________________________________

From: Discuss-gnuradio <discuss-gnuradio-bounces+e070832=hotmail.com@gnu.org> on behalf of David Cherkus <dcherkus@yahoo.com>
Sent: Monday, February 21, 2022 9:44 AM
To: GNURadio Discussion List
Subject: Re: Using VSCode With gr-tutorial

Thanks for the helpful info, Jeff.  I did try using the breakpoint window to clear all breakpoints last night and it didn't change anything.  I'll play around with it some more later today.  I'm a total noob with VS Code so it could be some form of 'user error'.

Regards,
Dave.