Hi Nicolas,
Thanks for the core file.
It seems to be a memory allocation issue for one of the glib2 object at first glance.
It also doesn't seem to be consistent and we haven't seen this kind of core dump in our environment.
Core was generated by `python3_32'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0xd7a09e40 in allocator_slab_stack_push (allocator=0xd7a09fc8 <allocator_add_slab+104>, ix=4053775540,
sinfo=0xb080ee4c) at gslice.c:1252
1252 gslice.c: No such file or directory.
[Current thread is 1 (process 1)]
(gdb) bt
#0 0xd7a09e40 in allocator_slab_stack_push (allocator=0xd7a09fc8 <allocator_add_slab+104>, ix=4053775540,
sinfo=0xb080ee4c) at gslice.c:1252
#1 0xd7a09fc8 in allocator_add_slab (allocator=0xd7a0a254 <slab_allocator_alloc_chunk+132>, ix=811461976,
chunk_size=804391072) at gslice.c:1285
#2 0xd7a0a254 in slab_allocator_alloc_chunk (chunk_size=3617623428) at gslice.c:1330
#3 0xd7a08d84 in magazine_cache_pop_magazine (ix=3617624504, countp=0x1) at gslice.c:726
#4 0xd7a091b8 in thread_memory_magazine1_reload (tmem=0xd7a096fc <g_slice_alloc+168>, ix=804391416)
at gslice.c:801
#5 0xd7a096fc in g_slice_alloc (mem_size=3617626080) at gslice.c:1014
#6 0xd7a097e0 in g_slice_alloc0 (mem_size=3618268168) at gslice.c:1051
#7 0xd7aa6408 in g_type_create_instance (type=3618197140) at gtype.c:1848
#8 0xd7a94e94 in g_object_new_internal (class=0xd7a955b8 <g_object_new_with_properties+716>,
params=0x30504858, n_params=1) at gobject.c:1799
........
(gdb) p prev
$6 = (SlabInfo *) 0x0
(gdb)
....
0xd7a09e3c <+140>: l r10,96(r31)
=> 0xd7a09e40 <+144>: st r10,8(r9)
0xd7a09e44 <+148>: l r9,96(r31)
.......
(gdb) p $r9
$3 = 0
Do you have ulimit values set to unlimited ?
I will try to find some more info from the core file.
------------------------------
SANGAMESH
------------------------------
Original Message:
Sent: Tue September 06, 2022 05:40 AM
From: Nicolas KAPLIN
Subject: dnf update "successfull" but "Segmentation fault(coredump)"
The core file...
------------------------------
Nicolas KAPLIN
Original Message:
Sent: Thu September 01, 2022 01:06 PM
From: SANKET RATHI
Subject: dnf update "successfull" but "Segmentation fault(coredump)"
Hi Christophe,
Sorry for delay in response. With the attached output it is hard to tell the core dump was from which application.
As dnf internally calls many other libraries and programs.
As you dnf check and update running later are fine so I don't think you have any issue.
But it is good to understand what caused the first core dump.
If you can attach the core file and provide more information about your system.
1. What level of AIX
2. Output of "rpm -qa"
3. output of "lslpp -l rpm.rte"
------------------------------
SANKET RATHI
Original Message:
Sent: Mon August 22, 2022 09:45 AM
From: christophe derouet
Subject: dnf update "successfull" but "Segmentation fault(coredump)"
Hello,
Please have a look to the enclosed file.
The "dnf update" is successfull but we have a return code 139 and a core dump.
Do we have to be worried about this ?
We ran "dnf check" two times.
We ran "dnf update" a second time but no update was available. Message "Nothing to do".
We thank you very much four help,
Christophe
ps : Maybe it comes from our AIX Operating System LPAR.
------------------------------
christophe derouet
------------------------------