Segfault under some conditions

[EternityForest]

I saw this error, and I'm not quite sure what's happening. I think jackd may have stopped in the background and restarted, it's a pretty complex environment, and there are also multiple threads.

Thought you guys might want to know about it anyway though.

Thanks for the great library!

Current thread 0x00007f6719361700 (most recent call first):
  File "/usr/lib/python3/dist-packages/jack.py", line 315 in owns
  File "/usr/lib/python3/dist-packages/jack.py", line 1377 in _wrap_port_ptr
  File "/usr/lib/python3/dist-packages/jack.py", line 1265 in get_port_by_name
  File "/usr/lib/python3/dist-packages/jack.py", line 1361 in _port_list_from_pointers
  File "/usr/lib/python3/dist-packages/jack.py", line 1329 in get_ports
  File "/home/daniel/Projects/KaithemAutomation/kaithem/src/jackmanager.py", line 1090 in _get_ports_fix
  File "/home/daniel/Projects/KaithemAutomation/kaithem/src/jackmanager.py", line 1170 in checkJackClient
  File "/home/daniel/Projects/KaithemAutomation/kaithem/src/jackmanager.py", line 1064 in work
  File "/usr/lib/python3.6/threading.py", line 864 in run
  File "/home/daniel/Projects/KaithemAutomation/kaithem/src/tweaks.py", line 42 in run_with_except_hook
  File "/usr/lib/python3.6/threading.py", line 916 in _bootstrap_inner
  File "/usr/lib/python3.6/threading.py", line 884 in _bootstrap

[SpotlightKid]

Where is the actual error message? This is only a traceback.

[EternityForest]

There isn't any that I can see. Do segmentation faults ever have anything more than that? AFAIK python has no way to handle them so there's never an exception.

…

On Tue, Sep 3, 2019, 7:46 AM Christopher Arndt ***@***.***> wrote: Where is the actual error message? This is only a traceback. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#70?email_source=notifications&email_token=AAFZCH7LSNP3MFNG5BFWYA3QHZ2GBA5CNFSM4ITCMFZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5YOF2A#issuecomment-527491816>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFZCH2IWL7TML4PKLBPXXLQHZ2GBANCNFSM4ITCMFZA> .

[SpotlightKid]

The traceback output must have come from somewhere. I believe that's from Python. To me that looks like a truncated exception message.

[EternityForest]

It's from the faulthandler module handling a SIGSEGV which doesn't generate an exception. There's no python exception just a notice that a segfault happened, and then everything stops.

…

On Tue, Sep 3, 2019, 11:32 AM Christopher Arndt ***@***.***> wrote: The traceback output must have come from somewhere. I believe that's from Python. To me that looks like a truncated exception message. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#70?email_source=notifications&email_token=AAFZCH5ZGONXWYKUBF6YT4DQH2UTNA5CNFSM4ITCMFZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5ZEPMA#issuecomment-527583152>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAFZCH3WTPBG2MTPAPRB2ZTQH2UTNANCNFSM4ITCMFZA> .

[mgeier]

@EternityForest Do you happen to use client.get_ports() with an invalid regular expression?
This could be #63?