The issue of the PID consistently being -1 in the parameters of the `bcc_resolve_symname` method

1. When using the bpf.attach_uprobe method in the BCC API, I encounter an issue where bcc fails to function as intended when the first parameter is c.

`ERROR : attach error: Unable to attach uprobe for binary c symbol malloc addr 0 offset 0 using alloc_enter`

I found that the issue arose due to an unexpected value in the binary_path parameter of bpf_attach_uprobe.

2. After bypassing this issue, the specified PID process events still cannot be collected as expected

```
int res = bcc_resolve_symname(binary_path.c_str(), symbol.c_str(),
symbol_addr, -1, nullptr, &output);
```