https://sourceware.org/bugzilla/show_bug.cgi?id=31103
--- Comment #12 from Di Chen ---
@fche
no problem, thanks for merging it :D
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=31103
Frank Ch. Eigler changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://sourceware.org/bugzilla/show_bug.cgi?id=31103
--- Comment #10 from Di Chen ---
Yes, patch submitted:
https://sourceware.org/pipermail/elfutils-devel/2024q1/006916.html
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=31103
--- Comment #9 from Frank Ch. Eigler ---
Yeah, OK, for a not-too-busy one, that sounds okay. Can you show a proposed
final diff?
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=31103
--- Comment #8 from Di Chen ---
Got it. I have used GDB to make debuginfod stop at
1) before malloc_trim(0)
$ cat /proc/$$/statm
228487 3456 2976 48 0 19049 0
2) after malloc_trim(0)
$ cat /proc/$$/statm
228462 3456 2976
https://sourceware.org/bugzilla/show_bug.cgi?id=31103
--- Comment #7 from Frank Ch. Eigler ---
Right, the linux kernel does not share enough memory consumption data in
rusage, so you need to read /proc/self/statm or such and compare its snapshots.
For memory release, it's not so much the size of
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,
https://sourceware.org/bugzilla/show_bug.cgi?id=31103
--- Comment #5 from Frank Ch. Eigler ---
Yeah, not surprised that there are no leaks. What this malloc_trim() and the
preceding sqlite3_db_release_memory() calls are supposed to do is to release
memory back to the operating system. So perhap
https://sourceware.org/bugzilla/show_bug.cgi?id=31103
--- Comment #4 from Di Chen ---
@fche, @mjw, @amerey
I don't have many clue about how to debug/measure this memory fluctuation
problem.
What I did:
1) use GDB to check the call graph.
thread_main_groom -> groom
-> sqlite3_db_
https://sourceware.org/bugzilla/show_bug.cgi?id=31103
Mark Wielaard changed:
What|Removed |Added
CC||mark at klomp dot org
--- Comment #3
https://sourceware.org/bugzilla/show_bug.cgi?id=31103
--- Comment #2 from Frank Ch. Eigler ---
Right, but the sqlite3* calls are still needed. I'm especially curious whether
any impact from the malloc_trim() is measurable.
--
You are receiving this mail because:
You are on the CC list for the
https://sourceware.org/bugzilla/show_bug.cgi?id=31103
--- Comment #1 from Di Chen ---
Hey Frank,
Are you talking about a change like this?
```
diff --git a/debuginfod/debuginfod.cxx b/debuginfod/debuginfod.cxx
index 524be948..fb9c1661 100644
--- a/debuginfod/debuginfod.cxx
+++ b/debuginfod/debu
https://sourceware.org/bugzilla/show_bug.cgi?id=31103
Di Chen changed:
What|Removed |Added
Assignee|unassigned at sourceware dot org |dichen at redhat dot com
13 matches
Mail list logo
