[Bug debuginfod/31480] New: debuginfod_find_debuginfo returns corrupt debuginfo file when out of memory

[amerey at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=31480

Bug ID: 31480
   Summary: debuginfod_find_debuginfo returns corrupt debuginfo
file when out of memory
   Product: elfutils
   Version: unspecified
Status: NEW
  Severity: normal
  Priority: P2
 Component: debuginfod
  Assignee: unassigned at sourceware dot org
  Reporter: amerey at redhat dot com
CC: elfutils-devel at sourceware dot org
  Target Milestone: ---

This bug has been seen when gdb ran out of memory while downloading from
debuginfod. See the following PR for more information: 

https://sourceware.org/bugzilla/show_bug.cgi?id=31478

It may be that libdebuginfod fails to unlink a partially downloaded file when
out-of-memory conditions are reached.  Reproducing this bug might be tricky.
We'll need to experiment with running gdb/debuginfod in a low memory
environment.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug debuginfod/31480] debuginfod_find_debuginfo returns corrupt debuginfo file when out of memory

[amerey at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=31480

Aaron Merey  changed:

   What|Removed |Added

   See Also||https://sourceware.org/bugz
   ||illa/show_bug.cgi?id=31478

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug debuginfod/31103] periodically malloc_trim()

[dichen at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=31103

--- Comment #6 from Di Chen  ---
Thanks Frank, I have debugged with rusage, but the difference between "during"
and "post" is not that obvious. I believe it's due to my small
.debuginfod.sqlite.

```
(gdb) p during
$2 = {ru_utime = {tv_sec = 0, tv_usec = 21790}, ru_stime = {tv_sec = 0, 
tv_usec = 29003}, {ru_maxrss = 103836, __ru_maxrss_word = 103836}, {
ru_ixrss = 0, __ru_ixrss_word = 0}, {ru_idrss = 0, __ru_idrss_word = 0}, {
ru_isrss = 0, __ru_isrss_word = 0}, {ru_minflt = 967, 
__ru_minflt_word = 967}, {ru_majflt = 0, __ru_majflt_word = 0}, {
ru_nswap = 0, __ru_nswap_word = 0}, {ru_inblock = 0, 
__ru_inblock_word = 0}, {ru_oublock = 128, __ru_oublock_word = 128}, {
ru_msgsnd = 0, __ru_msgsnd_word = 0}, {ru_msgrcv = 0, 
__ru_msgrcv_word = 0}, {ru_nsignals = 0, __ru_nsignals_word = 0}, {
ru_nvcsw = 1229, __ru_nvcsw_word = 1229}, {ru_nivcsw = 1, 
__ru_nivcsw_word = 1}}
(gdb) p post
$3 = {ru_utime = {tv_sec = 0, tv_usec = 21790}, ru_stime = {tv_sec = 0, 
tv_usec = 30393}, {ru_maxrss = 103836, __ru_maxrss_word = 103836}, {
ru_ixrss = 0, __ru_ixrss_word = 0}, {ru_idrss = 0, __ru_idrss_word = 0}, {
ru_isrss = 0, __ru_isrss_word = 0}, {ru_minflt = 967, 
__ru_minflt_word = 967}, {ru_majflt = 0, __ru_majflt_word = 0}, {
ru_nswap = 0, __ru_nswap_word = 0}, {ru_inblock = 0, 
__ru_inblock_word = 0}, {ru_oublock = 128, __ru_oublock_word = 128}, {
ru_msgsnd = 0, __ru_msgsnd_word = 0}, {ru_msgrcv = 0, 
__ru_msgrcv_word = 0}, {ru_nsignals = 0, __ru_nsignals_word = 0}, {
ru_nvcsw = 1273, __ru_nvcsw_word = 1273}, {ru_nivcsw = 1, 
__ru_nivcsw_word = 1}}


[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): grooming database
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): database record counts:
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): file d/e 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): file s 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): archive d/e 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): archive sref 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): archive sdef 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): buildids 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): filenames 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): fileparts 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): files scanned (#) 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): files scanned (mb) 0
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): index db size (mb) 21
[Thu 14 Mar 2024 03:22:47 AM GMT] (4738/4749): groomed database in 0.0129799s
```

Do you know where I can get a big .debuginfod.sqlite, so that I can measure the
performance on it?

-- 
You are receiving this mail because:
You are on the CC list for the bug.