Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support unordered .debug_info references to .debug_ranges #20

Closed
GoogleCodeExporter opened this issue May 27, 2015 · 4 comments
Closed

Comments

@GoogleCodeExporter
Copy link

As Ash <ashutoshkagrawal@gmail.com> reported,

"I am trying to create a shared library. My library gets generated
after the following warning. I have been able to use the library
successfully so far, but I am curious to know if something is wrong,
what does this warning mean and how to resolve this.

---

target SharedLib: libmytest (out/target/product/surf/obj/
SHARED_LIBRARIES/libmytest_intermediates/LINKED/libmytest.so)
target Prelink: libmytest (out/target/product/surf/symbols/system/lib/
libmytest.so)
libelfcopy: Warning: Location lists in .debug_info section aren't in
ascending order!
libelfcopy: Warning: Location offset 0x133d3 from CU 411 is not
preceded by the end of a location list, skipping...
target Strip: libmytest (out/target/product/surf/obj/lib/libmytest.so)
"

Jan Kratochvi mentioned that readelf had the same problem:
"
readelf sometimes complains on valid DWARF already produced by g++-4.3+:

readelf: Error: Range lists in .debug_info section aren't in ascending order!
readelf: Warning: Range lists in .debug_ranges section start at 0x60
"

http://sourceware.org/ml/binutils/2009-07/msg00123.html

So, improving libelfcopy might be a proper solution.

Original issue reported on code.google.com by jserv.tw@gmail.com on 3 Sep 2009 at 3:12

@GoogleCodeExporter
Copy link
Author

Notice: these messages were removed from donut branch.

Original comment by jserv.tw@gmail.com on 22 Oct 2009 at 3:51

@GoogleCodeExporter
Copy link
Author

Two approaches to resolve:
  - beagle-donut branch
  - latest toolchain with binutils fixes

The both were included.  Fxed

Original comment by jserv.tw@gmail.com on 25 Oct 2009 at 10:57

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Fixed in binutils, but it occurs in libelfcopy still.  Reopen.

Original comment by jserv.tw@gmail.com on 29 Oct 2009 at 7:05

  • Changed state: Accepted

@GoogleCodeExporter
Copy link
Author

Fix in commit eb10fd17d0deb295ec37bfca545106a9c7bee4f7

Original comment by jserv.tw@gmail.com on 29 Oct 2009 at 9:00

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant