Re: [iovisor-dev] Kernel crash when running bcc's test_xlate

2018-01-15 Thread Daniel Borkmann via iovisor-dev
On 01/11/2018 07:05 AM, Sandipan Das via iovisor-dev wrote: [...] > Any ideas about why this is happening? Also, it would be really helpful > if someone can translate the Pyroute2 calls in the test script to the > corresponding tc commands. I can trigger it as well, so I should have something

Re: [iovisor-dev] Kernel crash when running bcc's test_xlate

2018-01-15 Thread Daniel Borkmann via iovisor-dev
On 01/15/2018 09:33 PM, Daniel Borkmann via iovisor-dev wrote: > On 01/15/2018 09:13 PM, David Miller wrote: >> From: Daniel Borkmann via iovisor-dev >> Date: Mon, 15 Jan 2018 21:11:06 +0100 >> >>> On 01/15/2018 06:24 PM, Daniel Borkmann via iovisor-dev wrote:

Re: [iovisor-dev] Kernel crash when running bcc's test_xlate

2018-01-15 Thread David Miller via iovisor-dev
From: Daniel Borkmann via iovisor-dev Date: Mon, 15 Jan 2018 21:11:06 +0100 > On 01/15/2018 06:24 PM, Daniel Borkmann via iovisor-dev wrote: >> On 01/11/2018 07:05 AM, Sandipan Das via iovisor-dev wrote: >> [...] >>> Any ideas about why this is happening? Also, it

Re: [iovisor-dev] Kernel crash when running bcc's test_xlate

2018-01-15 Thread Daniel Borkmann via iovisor-dev
On 01/15/2018 06:24 PM, Daniel Borkmann via iovisor-dev wrote: > On 01/11/2018 07:05 AM, Sandipan Das via iovisor-dev wrote: > [...] >> Any ideas about why this is happening? Also, it would be really helpful >> if someone can translate the Pyroute2 calls in the test script to the >> corresponding

Re: [iovisor-dev] Kernel crash when running bcc's test_xlate

2018-01-15 Thread Daniel Borkmann via iovisor-dev
On 01/15/2018 09:13 PM, David Miller wrote: > From: Daniel Borkmann via iovisor-dev > Date: Mon, 15 Jan 2018 21:11:06 +0100 > >> On 01/15/2018 06:24 PM, Daniel Borkmann via iovisor-dev wrote: >>> On 01/11/2018 07:05 AM, Sandipan Das via iovisor-dev wrote: >>> [...]

Re: [iovisor-dev] How to use USDT probes without having to pass the pid of the traced program?

2018-01-15 Thread Sasha Goldshtein via iovisor-dev
Please note that some USDT probes have an associated "semaphore", which is really just a memory location that the probed code checks before actually invoking the probe. You cannot enable USDT probes that have a semaphore system-wide, without a process ID, because the semaphore location has to be

Re: [iovisor-dev] How to use USDT probes without having to pass the pid of the traced program?

2018-01-15 Thread Y Song via iovisor-dev
Kiran, Yes, tracing through USDT without PID should work. You can just remove "-p" parameter and give a try. Please try latest bcc as it fixed a few bugs. Let us know if you hit any issues. Yonghong On Mon, Jan 15, 2018 at 5:11 PM, Kiran T via iovisor-dev

[iovisor-dev] How to use USDT probes without having to pass the pid of the traced program?

2018-01-15 Thread Kiran T via iovisor-dev
Hi All the examples on tracing processes with USDT require the pid of the traced program: https://github.com/iovisor/bcc/tree/master/examples/tracing Can one not request to monitor binaries -- like with uprobes/uretprobes but with USDT? I am trying to trace php scripts running on a webserver,