[Bug threads/11581] 'set scheduler-locking on' should be automatic in response to SIGABRT and SIGSEGV

[Bug threads/11581] 'set scheduler-locking on' should be automatic in response to SIGABRT and SIGSEGV

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=11581

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
In https://sourceware.org/bugzilla/show_bug.cgi?id=11580#c3, Pedro
asked for no special casing like this.

It seems to me you could implement it yourself by using
"catch signal".  The commands could disable scheduler-locking.

I agree that some kind of warning when scheduler-locking can't
apply would be good to have.  Maybe it could be done once
per exec target.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug threads/11581] 'set scheduler-locking on' should be automatic in response to SIGABRT and SIGSEGV

[k04jg02 at gmail dot com]

------- Additional Comments From k04jg02 at gmail dot com  2010-05-07 18:53 -------
Also, due to some platforms supporting scheduler-locking and some not, and due
to developers that may use GDB across multiple platforms, it might be a good
idea to print a message when it's *not* being enabled in response to
SIGABRT/SIGSEGV due to lack of support, so that developers are aware GDB may act
differently than they're accustomed to from working on another platform.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11581

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.