crash-utility

It's this "largest" allocation size that's failing: [jfreyensee@fedora-virtualfedora Documentation]$ sudo crash -d4 crash 7.2.1-2.fc28 ... [ cut ] ... Linux version 5.0.16-100.fc28.x86_64 ([email protected]) (gcc version 8.3.1 20190223 (Red Hat 8.3.1-2)...

Unfortunately the issue in that bugzilla was addressed in crash-7.2.4. So I don't have a clue as to what the problem is.

----- Original Message ----- > Hi, > We are getting uptime values based off of jiffies values in crash. > Unfortunately, on arm64, the CPU frequency is assumed to be...

----- Original Message ----- > I start the domU with linux 4.12.13(bzImage) and xen 4.9.0, and I manually > dump the guest memory with `sudo xl dump-core myvm dump-res`. >...

----- Original Message ----- > i am using Linux 5.4 kernel, and found that there is a issue on crash. > This is a known issue. We are still waiting...

----- Original Message ----- > my question is the crash code should check the kernel version before you add > "TCR_EL1.T1SZ"? Well, it's essentially doing that by checking for the...

----- Original Message ----- > i check the v5.4.27, i seems not include this patch: > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm64/kernel/crash_core.c?h=v5.4.27 > That's unfortunate.

I don't know if this will help your cause, but I just checked this patch in: https://github.com/crash-utility/crash/commit/d379b47f04dc77ea1989609aca9bfd8d37b7b639 Introduce a new ARM64 "--machdep vabits_actual=" command line option for Linux 5.4 and...

----- Original Message ----- > I know i'm able to define macros in `~/.gdbinit` (just not interactively > using `define` from the `crash` prompt) > > hoping to have a...

----- Original Message ----- > but the `gdb` test I tested with was not attached to a running process either > (launched just as `$ gdb`) Yeah, hmmm, then I...