Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

BUG: Gdb or pycrash incorrectly resolve call frame.  #41

Copy link
Copy link
@firogh

Description

@firogh
Issue body actions

#1 0xffffffff861f45e2 in __vma_adjust (vma=0xffff9c037b421e10, start=, end=, pgoff=, insert=, expand=0xffff9c037b421e10) at ../mm/mmap.c:868
#2 0xffffffff861f544d in vma_adjust (insert=, pgoff=, end=, start=, vma=) at ../include/linux/mm.h:2104

The last arg, expand, of call frame #1, should be NULL since __vma_adjust is called from vma_adjust():
static inline int vma_adjust(struct vm_area_struct *vma, unsigned long start,
unsigned long end, pgoff_t pgoff, struct vm_area_struct *insert)
{
return __vma_adjust(vma, start, end, pgoff, insert, NULL);
}
vmcore@l3slave:/space/dumps/ziu/bsc1137008

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.