public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"developerdong@gmail.com" <developerdong@gmail.com>
Cc: "Dong, Zhi Bin" <ZhiBin.Dong@siemens.com>
Subject: Re: [PATCH] image: check if the file is core dump
Date: Tue, 16 Apr 2024 21:02:30 +0000	[thread overview]
Message-ID: <18fa0d57df55365ef4aeb0391593a213483a2197.camel@siemens.com> (raw)
In-Reply-To: <20240416051222.3344127-1-zhibin.dong@siemens.com>

On Tue, 2024-04-16 at 13:12 +0800, Zhibin Dong wrote:
> The previous code does a wrong judgement in two cases:
> 1. a file is suffixed by .core but is not a core dump file
> 2. a file is a core dump file but is not suffixed by .core

Hi, just for reference: This is an addition to the pattern implemented
in https://groups.google.com/g/isar-users/c/JtCExK7m4OY/m/F9QaxKBSAQAJ

> 
> The new code uses `file` to determine the type of files, which is
> more
> accurate.
> 
> Signed-off-by: Zhibin Dong <zhibin.dong@siemens.com>
> ---
>  meta/classes/image.bbclass | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 98741da0..10923947 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -444,7 +444,7 @@ EOSUDO
>  
>      # Sometimes qemu-user-static generates coredumps in chroot, move
> them
>      # to work temporary directory and inform user about it.
> -    for f in $(sudo find ${ROOTFSDIR} -type f -name *.core); do
> +    for f in $(sudo find ${ROOTFSDIR} -type f -exec file {} \; |

Are we sure this works in cross-arch scenarios? I.e. can an amd64
"file" detect arm64 coredumps? Did you test this Zhibin Dong?
If so, this patch is fine.

Best regards,
Felix

> grep 'core file' | cut -d: -f1); do
>          sudo mv "${f}" "${WORKDIR}/temp/"
>          bbwarn "found core dump in rootfs, check it in
> ${WORKDIR}/temp/${f##*/}"
>      done
> -- 
> 2.39.2
> 

-- 
Siemens AG, Technology
Linux Expert Center



  reply	other threads:[~2024-04-16 21:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AQHaj8I6385ePySTC0KmWAQOaNXsHbFrY0SA>
2024-04-16  5:12 ` Zhibin Dong
2024-04-16 21:02   ` MOESSBAUER, Felix [this message]
2024-04-17  2:11     ` Zhibin Dong
2024-04-17  4:57   ` Schmidt, Adriaan
2024-04-17  6:46   ` Zhibin Dong
2024-04-17  6:50     ` Zhibin Dong
2024-06-17  5:23       ` Uladzimir Bely
2024-06-27 15:44     ` Jan Kiszka
2024-07-01  4:56       ` Schmidt, Adriaan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18fa0d57df55365ef4aeb0391593a213483a2197.camel@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=ZhiBin.Dong@siemens.com \
    --cc=developerdong@gmail.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox