ChangeLog:

- Add ARM architecture support.
(leiwen@marvell.com)

- Fix wrongly using VM_ALWAYSDUMP value. On RHEL5, VM_ALWAYSDUMP is
defined as 0x04000000, but on RHEL6 and later upstream kernel, as
0x08000000. (0x08000000 had ever been used for VM_CAN_INVALIDATE
and now in the current 3.x version for VM_CAN_NONLINEAR.) Without
this fix, VDSO page is not included in a generated corefile. Then,
VDSO page is obviously not visible, and gdb displays broken
backtrace for the corefile where a task enters kernel mode via the
VDSO.

- Periodic updates following RHEL minor releases. See below for list
of the current supported kernels.

Supported Kernels:

* Upstream Kernels

version | x86 |x86_64| ARM
-----------+------+------+-----
2.6.35.7 | -- | -- | OK
2.6.36 | OK | OK | --
3.0.8 | -- | -- | OK

OK : Support
-- : Not support

* RHEL Kernels (#1

| x86 | x86_64
version | | 64 bit ; 32 bit
---------+------+--------+---------
4.8 | OK | OK | --
---------+------+--------+---------
5.5 | OK | OK | OK
5.6 | -- | OK | OK
5.7 | -- | OK | OK
5.8 | -- | OK | OK
---------+------+--------+---------
6.0 | OK | OK | OK
6.1 | -- | OK | OK
6.2 | -- | OK | OK

#1) RHEL4 is based on 2.6.9 kernel,
RHEL5 is based on 2.6.18 kernel and
RHEL6 is based on 2.6.32 kernel.

Note:

1) The versions signed OK are the ones I did verification. gcore
might work well on kernel versions near the supported ones.

2) The reason why I separate table for RHEL series and table for
upstream series is that RHEL kernels are being made based on upstream
kernels _plus a variety of additional patches_. So, rigorously, they
must be thought of as differnet kernels. However, just as 1), it
would be likely that gcore works well on vmcores for upstream kernels
near the corresponding RHEL versions.

Thanks.
HATAYAMA Daisuke
--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

Hi Daisuke,

Can you please format the crash-gcore-command-1.1.tar.gz file in
the same manner as crash-gcore-command-1.0.tar.gz? Here is the
current version:

# tar tvzmf crash-gcore-command-1.0.tar.gz
drwxrwxr-x hat/hat 0 2011-04-24 11:32 ./crash-gcore-command-1.0/
-rw-rw-r-- hat/hat 2038 2011-04-24 11:32 ./crash-gcore-command-1.0/gcore.mk
drwxrwxr-x hat/hat 0 2011-04-24 11:32 ./crash-gcore-command-1.0/libgcore/
-rw-rw-r-- hat/hat 4123 2011-04-24 11:32 ./crash-gcore-command-1.0/libgcore/gcore_verbose.c
-rw-rw-r-- hat/hat 64298 2011-04-24 11:32 ./crash-gcore-command-1.0/libgcore/gcore_x86.c
-rw-rw-r-- hat/hat 1007 2011-04-24 11:32 ./crash-gcore-command-1.0/libgcore/gcore_global_data.c
-rw-rw-r-- hat/hat 14664 2011-04-24 11:32 ./crash-gcore-command-1.0/libgcore/gcore_coredump_table.c
-rw-rw-r-- hat/hat 1102 2011-04-24 11:32 ./crash-gcore-command-1.0/libgcore/gcore_compat_x86.h
-rw-rw-r-- hat/hat 26629 2011-04-24 11:32 ./crash-gcore-command-1.0/libgcore/gcore_coredump.c
-rw-rw-r-- hat/hat 4893 2011-04-24 11:32 ./crash-gcore-command-1.0/libgcore/gcore_dumpfilter.c
-rw-rw-r-- hat/hat 10096 2011-04-24 11:32 ./crash-gcore-command-1.0/libgcore/gcore_elf_struct.c
-rw-rw-r-- hat/hat 27927 2011-04-24 11:32 ./crash-gcore-command-1.0/libgcore/gcore_defs.h
-rw-rw-r-- hat/hat 1619 2011-04-24 11:32 ./crash-gcore-command-1.0/libgcore/gcore_regset.c
-rw-rw-r-- hat/hat 17406 2011-04-24 11:32 ./crash-gcore-command-1.0/gcore.c
-rw-rw-r-- hat/hat 18015 2011-04-24 11:38 ./crash-gcore-command-1.0/COPYING
#

Your new release just dumps all the files into the current directory:

# tar xvzmf crash-gcore-command-1.1.tar.gz
gcore.c
gcore.mk
libgcore/
libgcore/gcore_compat_x86.h
libgcore/gcore_coredump.c
libgcore/gcore_coredump_table.c
libgcore/gcore_defs.h
libgcore/gcore_dumpfilter.c
libgcore/gcore_elf_struct.c
libgcore/gcore_global_data.c
libgcore/gcore_regset.c
libgcore/gcore_verbose.c
libgcore/gcore_x86.c
#

Thanks,
Dave

----- Original Message -----
>
> ChangeLog:
>
> - Add ARM architecture support.
> (leiwen@marvell.com)
>
> - Fix wrongly using VM_ALWAYSDUMP value. On RHEL5, VM_ALWAYSDUMP is
> defined as 0x04000000, but on RHEL6 and later upstream kernel, as
> 0x08000000. (0x08000000 had ever been used for VM_CAN_INVALIDATE
> and now in the current 3.x version for VM_CAN_NONLINEAR.) Without
> this fix, VDSO page is not included in a generated corefile. Then,
> VDSO page is obviously not visible, and gdb displays broken
> backtrace for the corefile where a task enters kernel mode via the
> VDSO.
>
> - Periodic updates following RHEL minor releases. See below for list
> of the current supported kernels.
>
> Supported Kernels:
>
> * Upstream Kernels
>
> version | x86 |x86_64| ARM
> -----------+------+------+-----
> 2.6.35.7 | -- | -- | OK
> 2.6.36 | OK | OK | --
> 3.0.8 | -- | -- | OK
>
> OK : Support
> -- : Not support
>
> * RHEL Kernels (#1
>
> | x86 | x86_64
> version | | 64 bit ; 32 bit
> ---------+------+--------+---------
> 4.8 | OK | OK | --
> ---------+------+--------+---------
> 5.5 | OK | OK | OK
> 5.6 | -- | OK | OK
> 5.7 | -- | OK | OK
> 5.8 | -- | OK | OK
> ---------+------+--------+---------
> 6.0 | OK | OK | OK
> 6.1 | -- | OK | OK
> 6.2 | -- | OK | OK
>
> #1) RHEL4 is based on 2.6.9 kernel,
> RHEL5 is based on 2.6.18 kernel and
> RHEL6 is based on 2.6.32 kernel.
>
> Note:
>
> 1) The versions signed OK are the ones I did verification. gcore
> might work well on kernel versions near the supported ones.
>
> 2) The reason why I separate table for RHEL series and table for
> upstream series is that RHEL kernels are being made based on
> upstream
> kernels _plus a variety of additional patches_. So, rigorously, they
> must be thought of as differnet kernels. However, just as 1), it
> would be likely that gcore works well on vmcores for upstream
> kernels
> near the corresponding RHEL versions.
>
> Thanks.
> HATAYAMA Daisuke
>
> --
> Crash-utility mailing list
> Crash-utility@redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility
>

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility

----- Original Message -----
> Hi HATAYAMA,
>
> > -----Original Message-----
> > From: HATAYAMA Daisuke [mailto:d.hatayama@jp.fujitsu.com]
> > Sent: Friday, March 23, 2012 8:38 AM
> > To: crash-utility@redhat.com; Lei Wen
> > Subject: Re: [Crash-utility] [ANNOUNCE] crash gcore command,
> > version 1.1
> > available
> >
> > From: Dave Anderson <anderson@redhat.com>
> > Subject: Re: [Crash-utility] [ANNOUNCE] crash gcore command,
> > version 1.1
> > available
> > Date: Thu, 22 Mar 2012 11:23:36 -0400 (EDT)
> >
> > > Can you please format the crash-gcore-command-1.1.tar.gz file in
> > > the same manner as crash-gcore-command-1.0.tar.gz? Here is the
> > > current version:
> >
> > Thanks for pointing out that, Dave. I attached new one.
> >
> > And for Lei, I made bigger fault that I missed arm source
> > file... Could you confirm that the new one can work on arm
> > environment?
>
> Yes, this version works for me.
>
> However, I think there is a point may need to be enhanced:
> diff --git a/extensions/libgcore/gcore_coredump.c
> b/extensions/libgcore/gcore_coredump.c
> index e2d9941..fec8ffc 100644
> --- a/extensions/libgcore/gcore_coredump.c
> +++ b/extensions/libgcore/gcore_coredump.c
> @@ -200,7 +200,8 @@ void gcore_coredump(void)
> "readmem vma list",
> gcore_verbose_error_handle());
> } else {
> - pagefaultf("page fault at %lx
", addr);
> + if (paddr == PADDR_NOT_AVAILABLE)
> + pagefaultf("page fault at %lx
", addr);
> BZERO(buffer, PAGE_SIZE);
> }
>
> Without this, I would see many " page fault at XXX" for the lazy
> mapping as we talked in the previous thread:
> http://www.redhat.com/archives/crash-utility/2012-February/msg00112.html

Given Daisuke's reply in http://www.redhat.com/archives/crash-utility/2012-February/msg00113.html:

I overlooked lazy allocation case in my explanation... In this sense,
the warning message might be unkind to users. Still, there's a way of
checking each page's status by a variety of crash sub-commands.

I was under the impression that Daisuke would prefer to keep the messages
in place in order to give the user notification that those pages are not
accessible. But I may have misunderstood his intentions.

In any case, since the new version functions correctly, I have posted
the version 1.1 on the extensions page.

Thanks,
Dave




--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility