Summary: | objdump: Out of memory in objalloc.c | ||
---|---|---|---|
Product: | binutils | Reporter: | spinpx <spinpx> |
Component: | binutils | Assignee: | Not yet assigned to anyone <unassigned> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | amodra |
Priority: | P2 | ||
Version: | 2.33 | ||
Target Milestone: | --- | ||
Host: | Target: | ||
Build: | Last reconfirmed: |
Description
spinpx
2019-02-19 09:45:51 UTC
Also report on https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89396 This doesn't reproduce for me, at least not on objdump built by gcc and without the address sanitizer (which increases memory use). Incidentally, hitting an out of memory failure in objalloc_alloc is not a libiberty failure and so should not be reported to the gcc project. Also, out of memory failures triggered by user input are not that interesting. It is perfectly reasonable for objdump to return with "out of memory" on objects with silly sizes. Also, the out-of-memory failure results in a further series of error messages starting with "corrupt size field in group section header: 0x6072740080". Related issue: https://sourceware.org/bugzilla/show_bug.cgi?id=24237 |