Here's an updated patch that adds a warning if the sscanf(3) line in gdb /linux-tdep.c fails. I've again verified locally that the patch causes gcore to generate a corefile such that gdb can generate an accurate backtrace from it.
I would appreciate review on the changes made to gdb/linux-tdep.c in the patch. It attempts to do what the prior version of the patch did, parsing /proc/PID/smaps instead of /proc/PID/maps and look for whether a few specific entries in each mapping are non-zero to indicate whether the mapping has been modified. The code in question was moved from gdb /linux-nat.c to gdb/linux-tdep.c and restructured to be line-oriented, which complicted things a bit. ** Patch added: "gdb-7.2-gcore-relro-writer.patch" https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/954714/+attachment/2873204/+files/gdb-7.2-gcore-relro-writer.patch ** Patch removed: "gdb-7.2-gcore-relro-writer.patch" https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/954714/+attachment/2867772/+files/gdb-7.2-gcore-relro-writer.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954714 Title: dropped patch reintroduces gcore relro backtrace problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/954714/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
