octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #59156] __debug_octave__ does not detect corre


From: Rik
Subject: [Octave-bug-tracker] [bug #59156] __debug_octave__ does not detect correctly macos
Date: Wed, 23 Sep 2020 11:12:51 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36

Follow-up Comment #9, bug #59156 (project octave):

This is most likely a Mac issue which does not relate to __debug_octave__. 
ls.m invokes system() and system() calls fork() and that library call on Mac
platforms is different from traditional UNIX.  Alternatively, the debugger
often has a way to determine what happens when a fork occurs: Do you follow
the parent or the child?  If lldb is following the child then a new thread
might be created, the shell launched, the ls command executed, and then the
thread stops and lldb complains.  Here's a Stack Overflow reference that might
help on Mac:
https://stackoverflow.com/questions/19204395/lldb-equivalent-of-gdbs-follow-fork-mode-or-detach-on-fork.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59156>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]