Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

platforms: remove usage of SIGCONT #13401

Closed
wants to merge 1 commit into from
Closed

Conversation

julianoes
Copy link
Contributor

@julianoes julianoes commented Nov 6, 2019

I was wondering if this was still required or how this worked but it seems like it still works without.

The reason I looked into SIGCONT was that lldb in vscode does currently
not ignore the signal as it should.

@bkueng @dagar what am I missing?

I was wondering if this was still required or how this worked but it
seems like it still works without.

The reason I looked into SIGCONT was that lldb in vscode does currently
not ignore the signal as it should.
@bkueng
Copy link
Member

bkueng commented Nov 6, 2019

From what I know this is required. You need this in your ~/.gdbinit:

handle SIGCONT nostop noprint nopass

@dagar
Copy link
Member

dagar commented Nov 6, 2019

We should take a closer look to see what's actually happening with "HRT" in this case.

For the regular work queues (HPWORK and LPWORK ported from NuttX), we're pretty close to being able to delete them entirely. #12068

@julianoes
Copy link
Contributor Author

@bkueng in theory the SIGCONT signal is ignored in lldb ran by vscode, in practice unfortunately not: https://discuss.px4.io/t/vscode-lldb-debugging-paused-on-exception/13512/11

@julianoes
Copy link
Contributor Author

@dagar ok cool, let's continue with moving everything over and then getting rid of them.

@dagar dagar closed this Jan 22, 2020
@julianoes
Copy link
Contributor Author

@dagar is this gone already?

@julianoes julianoes deleted the pr-remove-sigcont branch January 24, 2020 08:15
@julianoes
Copy link
Contributor Author

Follow up in #12068.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants