pixie-io / pixie-demos Goto Github PK

sudo ./openssl_tracer 1634608
In file included from <built-in>:2:
In file included from /virtual/include/bcc/bpf.h:12:
In file included from include/linux/types.h:6:
In file included from include/uapi/linux/types.h:14:
In file included from include/uapi/linux/posix_types.h:5:
In file included from include/linux/stddef.h:5:
In file included from include/uapi/linux/stddef.h:2:
In file included from include/linux/compiler_types.h:80:
include/linux/compiler-clang.h:41:9: warning: '__HAVE_BUILTIN_BSWAP32__' macro redefined [-Wmacro-redefined]
#define __HAVE_BUILTIN_BSWAP32__
        ^
<command line>:4:9: note: previous definition is here
#define __HAVE_BUILTIN_BSWAP32__ 1
        ^
In file included from <built-in>:2:
In file included from /virtual/include/bcc/bpf.h:12:
In file included from include/linux/types.h:6:
In file included from include/uapi/linux/types.h:14:
In file included from include/uapi/linux/posix_types.h:5:
In file included from include/linux/stddef.h:5:
In file included from include/uapi/linux/stddef.h:2:
In file included from include/linux/compiler_types.h:80:
include/linux/compiler-clang.h:42:9: warning: '__HAVE_BUILTIN_BSWAP64__' macro redefined [-Wmacro-redefined]
#define __HAVE_BUILTIN_BSWAP64__
        ^
<command line>:5:9: note: previous definition is here
#define __HAVE_BUILTIN_BSWAP64__ 1
        ^
In file included from <built-in>:2:
In file included from /virtual/include/bcc/bpf.h:12:
In file included from include/linux/types.h:6:
In file included from include/uapi/linux/types.h:14:
In file included from include/uapi/linux/posix_types.h:5:
In file included from include/linux/stddef.h:5:
In file included from include/uapi/linux/stddef.h:2:
In file included from include/linux/compiler_types.h:80:
include/linux/compiler-clang.h:43:9: warning: '__HAVE_BUILTIN_BSWAP16__' macro redefined [-Wmacro-redefined]
#define __HAVE_BUILTIN_BSWAP16__
        ^
<command line>:3:9: note: previous definition is here
#define __HAVE_BUILTIN_BSWAP16__ 1
        ^
3 warnings generated.
prog tag mismatch 9f16ca2b9f8b1e01 1
WARNING: cannot get prog tag, ignore saving source with program tag
Attached uprobe to binary /usr/lib/x86_64-linux-gnu/libssl.so.1.1 at symbol SSL_write
prog tag mismatch c4b89df08a974514 1
WARNING: cannot get prog tag, ignore saving source with program tag
Attached uprobe to binary /usr/lib/x86_64-linux-gnu/libssl.so.1.1 at symbol SSL_write
prog tag mismatch 9f16ca2b9f8b1e01 1
WARNING: cannot get prog tag, ignore saving source with program tag
Attached uprobe to binary /usr/lib/x86_64-linux-gnu/libssl.so.1.1 at symbol SSL_read
prog tag mismatch 12c46cd71c0a6c20 1
WARNING: cannot get prog tag, ignore saving source with program tag
Attached uprobe to binary /usr/lib/x86_64-linux-gnu/libssl.so.1.1 at symbol SSL_read
Opened perf buffer tls_events
Successfully deployed BPF probes. Tracing for SSL data. Use Ctrl-C to exit.

clang++ --std=c++17 -o perf_profiler perf_profiler.cc -lbcc
/tmp/perf_profiler-0943c5.o: In function `ebpf::BPF::BPF(unsigned int, ebpf::TableStorage*)':
perf_profiler.cc:(.text._ZN4ebpf3BPFC2EjPNS_12TableStorageE[_ZN4ebpf3BPFC2EjPNS_12TableStorageE]+0x56): undefined reference to `ebpf::BPFModule::BPFModule(unsigned int, ebpf::TableStorage*)'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Makefile:21: recipe for target 'perf_profiler' failed
make: *** [perf_profiler] Error 1

// This needs to match exactly with the Go version of the struct.
struct syscall_write_event_t {
  // We split attributes into a separate struct, because BPF gets upset if you do lots of
  // size arithmetic. This makes it so that it's attributes followed by message.
  struct attr_t {
    int event_type;
    int fd;
    int bytes;
    // Care needs to be taken as only msg_size bytes of msg are guaranteed
    // to be valid.
    int msg_size;
  } attr;
  char msg[MAX_MSG_SIZE];
}; ```

Could I possibly have a link to the go documentation where it specifies that this struct syscall_write_event_t
 is as given. Also, if the program would be compiled in the future with python or another language, 
would I have to then use the documentation of given language for this struct. If anyone has the 
link of relevant documentation for python or C, please let me know! 

Thanks