"bpftool prog list" command displays eBPF program name if available.
Also, the crash "bpf -m|-M" options display eBPF map name. But the
"bpf -p|-P" options don't display its name. It would be useful in
finding the program which we want to see.
Signed-off-by: Kazuhito Hagio
---
bpf.c | 12
> > I suspect that it's a problem with either the --kaslr offset and/or
> > the phys_base value that you have used.
>
> Is there method to know or print kaslr & phy_base in a running Linux system?
They are normally passed in the VMCOREINFO data that is contained in an ELF
PT_NOTE
in the
On Wed, Mar 4, 2020 at 2:49 PM Dave Anderson wrote:
>
> > Hello List,
> >
> > I've a two ELF coredumps from two different HyperV VMs generated by this
> > tool (https://github.com/Azure/azure-linux-utils/tree/master/vm2core).
> >
> > Crash works with one of these coredumps but do not work with
On Thu, Mar 5, 2020 at 12:19 PM Santosh wrote:
>
> On Wed, Mar 4, 2020 at 2:49 PM Dave Anderson wrote:
> >
> > > Hello List,
> > >
> > > I've a two ELF coredumps from two different HyperV VMs generated by this
> > > tool (https://github.com/Azure/azure-linux-utils/tree/master/vm2core).
> > >
> >
- Original Message -
> > Is there method to know or print kaslr & phy_base in a running Linux
> > system?
>
> Got it.
>
> crash> p vmcoreinfo_data+1600
> $12 = (unsigned char *) 0x90ff7cdc3640
>
- Original Message -
> "bpftool prog list" command displays eBPF program name if available.
> Also, the crash "bpf -m|-M" options display eBPF map name. But the
> "bpf -p|-P" options don't display its name. It would be useful in
> finding the program which we want to see.
Looks good
On Thu, Mar 5, 2020 at 12:54 PM Dave Anderson wrote:
>
> > > I suspect that it's a problem with either the --kaslr offset and/or
> > > the phys_base value that you have used.
> >
> > Is there method to know or print kaslr & phy_base in a running Linux system?
>
> They are normally passed in the
On Thu, Mar 5, 2020 at 1:07 PM Santosh wrote:
>
> On Thu, Mar 5, 2020 at 12:54 PM Dave Anderson wrote:
> >
> > > > I suspect that it's a problem with either the --kaslr offset and/or
> > > > the phys_base value that you have used.
> > >
> > > Is there method to know or print kaslr & phy_base in
