Date: Sat, 3 Apr 2021 09:53:38 +0200 From: Andrea Venturoli <ml@netfence.it> To: yuri@FreeBSD.org Cc: freebsd-questions@FreeBSD.org Subject: Re: devel/google-perftools in a jail Message-ID: <2fde0431-a9b2-ac42-c34b-8b2f312ddb85@netfence.it> In-Reply-To: <85f65024-2c3e-b83e-da5a-21d522a92bc6@rawbw.com> References: <cc269448-4906-2dc2-8b46-10329d71ed7a@netfence.it> <18dcbb14-d208-071e-8f93-39dd45d7dc14@rawbw.com> <2cfa2de6-3d22-bc88-90d2-49e94d1a8f0d@netfence.it> <d5694a9d-7fcc-12ea-08d9-2f34d4d89f88@rawbw.com> <f15950f6-5727-1f54-ff18-c43c144d971c@netfence.it> <85f65024-2c3e-b83e-da5a-21d522a92bc6@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/2/21 9:13 PM, yuri@FreeBSD.org wrote: > On 4/2/21 4:56 AM, Andrea Venturoli wrote: >>> Is the string '/usr/jails/' present in prof.out? >> >> Yes. > > > Was the profiling session run on the same system/in the same jail? Yes. All is happening *inside* the jail > Did these files exist right after the profiling session? No (again, not in the jail POV). I think perftools-pprof queries for a given library and, instead of the path in the jail's filesystem space, somehow gets the same file but in the host's filesystem space. I don't know how it tries to get these, though. > Profiling session and display session should run on exactly same > system/same jail. That's what I'm doing. > Besides, even when run in jail, jail paths aren't visible to regular > executables because jail runs in chroot environment. s/aren't visible/shouldn't be visible/ !!! > This error should be impossible - something really weird occurred. Never mind; I've moved to another tool meanwhile. If you want me to open a bug report for the record, just ask. bye & Thanks av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2fde0431-a9b2-ac42-c34b-8b2f312ddb85>