$ ./gdb -nx -q --data-directory=data-directory ~/a.out -ex "set confirm off" -ex "file -readnow ~/a.out" http://www-look-4.com/category/technology/ Reading symbols from /home/simark/a.out... Reading symbols from ~/a.out... /home/simark/src/binutils-gdb/gdb/dwarf2/read.c:8098: https://komiya-dental.com/shopping/safety-for-online-shopping/ internal-error: void create_all_comp_units(dwarf2_per_objfile*): Assertion `per_objfile->per_bfd->all_comp_units.empty ()' failed. http://www.iu-bloomington.com/health/health-and-cannabis/ This is a recurring problem that exposes a design issue in the DWARF per-BFD sharing feature. Things work well when loading a binary with https://waytowhatsnext.com/crypto/bought-house-with-bitcoin/ the same method (with/without index, with/without readnow) twice in a row. But they don't work so well when loading a binary with different methods. See this previous fix, for example: http://www.wearelondonmade.com/category/health/ efb763a5ea35 ("gdb: check for partial symtab presence in dwarf2_initialize_objfile") That one handled the case where the first load is normal (uses partial symbols) and the second load uses an index. http://www.jopspeech.com/category/services/ The problem is that when loading an objfile with a method A, we create a dwarf2_per_bfd and some dwarf2_per_cu_data and initialize them with the data belonging to that method. http://joerg.li/category/health/ When loading another obfile sharing the same BFD but with a different method B, it's not clear how to re-use the dwarf2_per_bfd/dwarf2_per_cu_data previously created, because they contain the data specific to method A http://connstr.net/category/health/ $ ./gdb -nx -q --data-directory=data-directory ~/a.out -ex "set confirm off" -ex "file -readnow ~/a.out" http://embermanchester.uk/category/health/ Reading symbols from /home/simark/a.out... Reading symbols from ~/a.out... /home/simark/src/binutils-gdb/gdb/dwarf2/read.c:8098: internal-error: void create_all_comp_units(dwarf2_per_objfile*): Assertion http://www.slipstone.co.uk/category/health/ `per_objfile->per_bfd->all_comp_units.empty ()' failed. This is a recurring problem that exposes a design issue in the DWARF http://www.logoarts.co.uk/category/services/ per-BFD sharing feature. Things work well when loading a binary with the same method (with/without index, with/without readnow) twice in a row. But they don't work so well when http://www.acpirateradio.co.uk/category/tech/ loading a binary with different methods. See this previous fix, for example: efb763a5ea35 ("gdb: check for partial symtab presence in dwarf2_initialize_objfile") http://www.compilatori.com/category/health/ That one handled the case where the first load is normal (uses partial symbols) and the second load uses an index. The problem is that when loading an objfile with a method A, we create a dwarf2_per_bfd and some dwarf2_per_cu_data and initialize them with the data belonging to that method. When loading another obfile sharing the same BFD but with a different method B, it's not clear how to re-use the dwarf2_per_bfd/dwarf2_per_cu_data previously created, because they contain the data specific to method A https://www.webb-dev.co.uk/health/health-and-cannabis/ $ ./gdb -nx -q --data-directory=data-directory ~/a.out -ex "set confirm off" -ex "file -readnow ~/a.out" Reading symbols from /home/simark/a.out... Reading symbols from ~/a.out... /home/simark/src/binutils-gdb/gdb/dwarf2/read.c:8098: internal-error: void create_all_comp_units(dwarf2_per_objfile*): Assertion `per_objfile->per_bfd->all_comp_units.empty ()' failed. This is a recurring problem that exposes a design issue in the DWARF per-BFD sharing feature. Things work well when loading a binary with the same method (with/without index, with/without readnow) twice in a row. But they don't work so well when loading a binary with different methods. See this previous fix, for example: efb763a5ea35 ("gdb: check for partial symtab presence in dwarf2_initialize_objfile"
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/413278 Title: stack protector guard value does not lead with a NULL byte Status in GLibC: Fix Released Status in eglibc package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Invalid Status in eglibc source package in Jaunty: Invalid Status in glibc source package in Jaunty: Fix Released Status in eglibc source package in Karmic: Fix Released Status in glibc source package in Karmic: Invalid Bug description: IMPACT: stack protections are weakened due to strcpy function being able to write the stack guard (since it does not start with a zero byte). ADDRESSED: correctly implement leading zero, as done in Karmic. DISCUSSION: regression potential is low, since the patch is isolated and well tested. TEST CASE: $ bzr branch lp:~ubuntu-bugcontrol/qa-regression-testing/master qa-regression-testing $ cd qa-regression-testing/scripts $ ./test-glibc-security.py -v Build helper tools ... (9.10) ok glibc heap protection ... ok sprintf not pre-truncated with -D_FORTIFY_SOURCE=2 ... ok glibc pointer obfuscation ... ok Password hashes ... (sha512) ok Stack guard exists ... ok Stack guard leads with zero byte ... FAIL Stack guard is randomized ... ok ====================================================================== FAIL: Stack guard leads with zero byte ---------------------------------------------------------------------- Traceback (most recent call last): File "./test-glibc-security.py", line 170, in test_81_stack_guard_leads_zero self.assertEqual(one.startswith('00 '), expected, one) AssertionError: 62 55 59 69 cd 20 39 80 ---------------------------------------------------------------------- Ran 8 tests in 0.145s FAILED (failures=1) expected outcome: 0 failures. ProblemType: Bug Architecture: amd64 Date: Thu Aug 13 13:59:02 2009 Dependencies: findutils 4.4.2-1 gcc-4.4-base 4.4.1-1ubuntu3 libc6 2.10.1-0ubuntu6 libgcc1 1:4.4.1-1ubuntu3 DistroRelease: Ubuntu 9.10 Package: libc6 2.10.1-0ubuntu6 ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-5.24-generic SourcePackage: eglibc Uname: Linux 2.6.31-5-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/413278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
