[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#932250: linux-image-amd64: adding segfault data



Control: tag -1 - moreinfo
Control: tag -1 help

On Wed, 17 Jul 2019 01:41:16 +0200 m.alfaeko@gmail.com wrote:
> Package: linux-image-amd64
> Version: 4.19+105
> Followup-For: Bug #932250
> 
> adding file with segfault data

For some reason I didn't look at this until now.  The contents are:

xfdesktop[11344]: segfault at 16 ip 00007ff9fd0f29ea sp 00007ffffb934f00 error 4 in libglib-2.0.so.0.5800.3[7ff9fd0a2000+7e000]
2019-07-17T01:04:04.589422+02:00 debian kernel: [18604.040877] Code: 8d 48 ff 48 89 c3 49 89 ce 49 c1 e6 04 4c 01 f5 48 8b 45 00 48 85 c0 0f 84 c3 00 00 00 48 8b 58 08 48 85 db 0f 84 fe 01 00 00 <48> 8b 13 48 89 50 08 48 8b 45 08 48 85 c0 74 08 48 83 e8 01 48 89
xfdesktop[16727]: segfault at 16 ip 00007fe22e9aa9ea sp 00007ffd313bc000 error 4 in libglib-2.0.so.0.5800.3[7fe22e95a000+7e000]
2019-07-17T01:04:07.231175+02:00 debian kernel: [18606.685725] Code: 8d 48 ff 48 89 c3 49 89 ce 49 c1 e6 04 4c 01 f5 48 8b 45 00 48 85 c0 0f 84 c3 00 00 00 48 8b 58 08 48 85 db 0f 84 fe 01 00 00 <48> 8b 13 48 89 50 08 48 8b 45 08 48 85 c0 74 08 48 83 e8 01 48 89
gmain[16752]: segfault at 17 ip 00007fdada99a9ea sp 00007fdad7f7c7c0 error 4 in libglib-2.0.so.0.5800.3[7fdada94a000+7e000]
2019-07-17T01:04:21.214468+02:00 debian kernel: [18620.669154] Code: 8d 48 ff 48 89 c3 49 89 ce 49 c1 e6 04 4c 01 f5 48 8b 45 00 48 85 c0 0f 84 c3 00 00 00 48 8b 58 08 48 85 db 0f 84 fe 01 00 00 <48> 8b 13 48 89 50 08 48 8b 45 08 48 85 c0 74 08 48 83 e8 01 48 89
gmain[16974]: segfault at 1c ip 00007f3b5dcc29ea sp 00007f3b5b2a45f0 error 4 in libglib-2.0.so.0.5800.3[7f3b5dc72000+7e000]
2019-07-17T01:05:28.070894+02:00 debian kernel: [18687.524814] Code: 8d 48 ff 48 89 c3 49 89 ce 49 c1 e6 04 4c 01 f5 48 8b 45 00 48 85 c0 0f 84 c3 00 00 00 48 8b 58 08 48 85 db 0f 84 fe 01 00 00 <48> 8b 13 48 89 50 08 48 8b 45 08 48 85 c0 74 08 48 83 e8 01 48 89

These segfaults at least don't seem so random.  Every single one is in
the same code in libglib-2.0.so.0.5800.3.  (The ip addresses differ due
to ASLR, but the offsets are the same.)  The code bytes correspond to
part of the g_slice_alloc() function.

That seems more likely to be a bug in libglib, or perhaps some
intermediate library.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                         - Albert Camus

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: