[Bug tools/29719] eu-readelf -s=section is confusing
https://sourceware.org/bugzilla/show_bug.cgi?id=29719 --- Comment #3 from Martin Liska --- (In reply to Mark Wielaard from comment #2) > I like the WARNING idea. This would also help with something like: > $ eu-readelf --symbols=.dynsyms /bin/bash > Which currently says nothing, but should warn (it is .dynsym without the s). Great, can you please take the suggested patch and add a test-case for it? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
[PATCH] debuginfod: Initialize response_data early in debuginfod-client query
On error going to out2, the response_data is freed. So initialize the response_data to NULL immediately after allocation or when going back to query_in_parallel. Signed-off-by: Mark Wielaard --- debuginfod/ChangeLog | 5 + debuginfod/debuginfod-client.c | 4 ++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git a/debuginfod/ChangeLog b/debuginfod/ChangeLog index 5678002a..2a9ba518 100644 --- a/debuginfod/ChangeLog +++ b/debuginfod/ChangeLog @@ -1,3 +1,8 @@ +2022-11-15 Mark Wielaard + + * debuginfod-client.c (debuginfod_query_server): Initialize + response_data early. + 2022-11-04 Aaron Merey * debuginfod-client.c (debuginfod_find_section): Ensure rc diff --git a/debuginfod/debuginfod-client.c b/debuginfod/debuginfod-client.c index 99da05ef..c92ef274 100644 --- a/debuginfod/debuginfod-client.c +++ b/debuginfod/debuginfod-client.c @@ -1250,6 +1250,8 @@ debuginfod_query_server (debuginfod_client *c, data[i].handle = NULL; data[i].fd = -1; data[i].errbuf[0] = '\0'; + data[i].response_data = NULL; + data[i].response_data_size = 0; } char *escaped_string = NULL; @@ -1346,8 +1348,6 @@ debuginfod_query_server (debuginfod_client *c, curl_easy_setopt_ck (data[i].handle, CURLOPT_LOW_SPEED_LIMIT, 100 * 1024L); } - data[i].response_data = NULL; - data[i].response_data_size = 0; curl_easy_setopt_ck(data[i].handle, CURLOPT_FILETIME, (long) 1); curl_easy_setopt_ck(data[i].handle, CURLOPT_FOLLOWLOCATION, (long) 1); curl_easy_setopt_ck(data[i].handle, CURLOPT_FAILONERROR, (long) 1); -- 2.18.4
[Bug tools/29786] New: Unable to understand, in objdump, the user is not using the name, so using a.out
https://sourceware.org/bugzilla/show_bug.cgi?id=29786
Bug ID: 29786
Summary: Unable to understand, in objdump, the user is not
using the name, so using a.out
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tools
Assignee: unassigned at sourceware dot org
Reporter: zhuorong.lin at outlook dot com
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Unable to understand, in objdump, the user is not using the name, so using
a.out
Why not use an empty string?
elfutils-0.187\src\objdump.c
```
if (remaining == argc)
/* The user didn't specify a name so we use a.out. */
result = process_file ("a.out", false);
```
--
You are receiving this mail because:
You are on the CC list for the bug.
[Bug tools/29786] Unable to understand, in objdump, the user is not using the name, so using a.out
https://sourceware.org/bugzilla/show_bug.cgi?id=29786 Frank Ch. Eigler changed: What|Removed |Added Resolution|--- |NOTABUG CC||fche at redhat dot com Status|UNCONFIRMED |RESOLVED --- Comment #1 from Frank Ch. Eigler --- Why not use an empty string as a filename? A user can type eu-objdump "" to pass an empty string if that's really what she wants. Defaulting to "a.out" in the absence of a filename is traditional. -- You are receiving this mail because: You are on the CC list for the bug.
elfutils-devel@sourceware.org
This Friday, 18 November, at 16:00 UTC (11:00am Eastern, 17:00 Central European Time) the FSF will host a session on their BBB server about the current sourceware infrastructure and future plans. https://www.fsf.org/events/sourceware-infrastructure-a-presentation-and-community-q-a https://inbox.sourceware.org/overseers/6e9cde97-d880-5343-6cfd-16a648cf6...@fsf.org/ We like to discuss how to use the new infrastructure setup this last year, builder, try/ci/full buildbots, bunsen testsuite analysis, patchwork patch tracking, handling patches/email with public-inbox, b4, the sourcehut mirror. And the future of Sourceware as a Software Freedom Conservancy member project. (*) This presentation is for everybody who likes to discuss (and wants to help with) automating the infrastructure to make contributing to our projects more fun and more productive. (*) Similar to the BoF we intended to do at the Cauldron this year: https://gnu.wildebeest.org/~mark/sourceware/presentation.html
