I have a small program that will reproduce the issue. Where should the bug be sent? It's pretty serious. The system is forgetting the location of the current working directory in a recursive call.
On Fri, Jan 13, 2017 at 9:30 AM, Nahum Shalman <nshal...@omniti.com> wrote: > Have you tried simply tracing the lx-syscall probes? > > On Fri, Jan 13, 2017 at 9:24 AM, Mini Trader <miniflowtra...@gmail.com> > wrote: > >> I followed these instructions prior to my post and my zone would not boot >> after doing the mod to add the flag to the file. >> >> >> On Fri, Jan 13, 2017 at 8:55 AM Nahum Shalman <nshal...@omniti.com> >> wrote: >> >>> The short answer is yes. >>> >>> My experience debugging LX was on SmartOS and there are some notes on >>> https://wiki.smartos.org/display/DOC/LX+Branded+Zones#LXB >>> randedZones-Debugging >>> >>> Some of the details on that page are Specific to SmartOS, but some of it >>> is generic to LX. >>> >>> -Nahum >>> >>> On Fri, Jan 13, 2017 at 12:46 AM, Mini Trader <miniflowtra...@gmail.com> >>> wrote: >>> >>> Is there anything that can be done to trace a program having issues on >>> an LX Zone. >>> >>> I am seeing: >>> >>> OSError: [Errno 2] No such file or directory: >>> >>> Again under certain conditions which I am trying to trace - >>> unfortunately this is a closed source program. Can DTrace be used to help >>> track something like this? >>> >>> Thanks! >>> >>> >>> >>> _______________________________________________ >>> >>> >>> OmniOS-discuss mailing list >>> >>> >>> OmniOS-discuss@lists.omniti.com >>> >>> >>> http://lists.omniti.com/mailman/listinfo/omnios-discuss >>> >>> >>> >>> >>> >>> >>> >
_______________________________________________ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss