public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug corefiles/11804] Fix -Wl,-z,relro gcore writer (+maybe reader)
Date: Tue, 31 Aug 2010 11:26:00 -0000	[thread overview]
Message-ID: <20100831112655.2522.qmail@sourceware.org> (raw)
In-Reply-To: <20100710211433.11804.jan.kratochvil@redhat.com>


------- Additional Comments From rguenth at gcc dot gnu dot org  2010-08-31 11:26 -------
Hm, it doesn't seem to work reliably for me (it works for dumping core of
/bin/sleep).  If I dump core of a running /usr/lib/postfix/qmgr on load
I get

# gdb /usr/lib/postfix/qmgr
Reading symbols from /usr/lib/postfix/qmgr...Missing separate debuginfo for
/usr/lib/postfix/qmgr
Try: zypper install -C
"debuginfo(build-id)=a67933b04330530f5e80941c968ba3623b1fd5ac"
(no debugging symbols found)...done.
(gdb) set debug solib
(gdb) set verbose
(gdb) core core.4529
svr4_current_sos: exec_bfd /usr/lib/postfix/qmgr
elf_locate_base: found program entry address 0x7fac68ab63a0 for
/usr/lib/postfix/qmgr
elf_locate_base: expected relocation offset 0x7fac68ab2000 for /usr/lib/postfix/qmgr
elf_locate_base: .dynamic section found in /usr/lib/postfix/qmgr
elf_locate_base: .dynamic addr 0x20fbc0
elf_locate_base: read in .dynamic section
elf_locate_base: tag at offset 0x0 is not readable, dropping relocation offset
0x7fac68ab2000
elf_locate_base: found program entry address 0x7fac68ab63a0 for
/usr/lib/postfix/qmgr
elf_locate_base: expected relocation offset 0x7fac68ab2000 for /usr/lib/postfix/qmgr
elf_locate_base: .dynamic section found in /usr/lib/postfix/qmgr
elf_locate_base: .dynamic addr 0x20fbc0
elf_locate_base: read in .dynamic section
elf_locate_base: tag at offset 0x0 is not readable, dropping relocation offset
0x7fac68ab2000
elf_locate_base: unrelocated ptr addr 0x20fd18
elf_locate_base: relocated ptr addr 0x20fd18 (relocation offset 0x0) for
/usr/lib/postfix/qmgr
elf_locate_base: Tag entry has value 0x0 -- return now
svr4_current_sos: no DT_DEBUG found in /usr/lib/postfix/qmgr -- return now

the program address looks good, the .dynamic section in the running process
is mapped like

7fac68cc1000-7fac68cc2000 r--p 0000f000 08:06 360346                     /usr/li
b/postfix/qmgr
Size:                  4 kB
Rss:                   4 kB
Pss:                   4 kB
Shared_Clean:          0 kB
Shared_Dirty:          0 kB
Private_Clean:         4 kB
Private_Dirty:         0 kB
Referenced:            4 kB
Swap:                  0 kB
KernelPageSize:        4 kB
MMUPageSize:           4 kB
7fac68cc2000-7fac68cc3000 rw-p 00010000 08:06 360346                     /usr/li
b/postfix/qmgr
Size:                  4 kB
Rss:                   4 kB
Pss:                   4 kB
Shared_Clean:          0 kB
Shared_Dirty:          0 kB
Private_Clean:         0 kB
Private_Dirty:         4 kB
Referenced:            4 kB
Swap:                  0 kB
KernelPageSize:        4 kB
MMUPageSize:           4 kB
7fac68cc3000-7fac68cfe000 rw-p 00000000 00:00 0                          [heap]

thus the relocated address should be not in the core file but taken from
/usr/lib/postfix/qmgr - but that fails.  Is this not available at this point
or where do I need to dig?  I'm not too familiar with the gdb codebase...

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenth at gcc dot gnu dot
                   |                            |org


http://sourceware.org/bugzilla/show_bug.cgi?id=11804

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2010-08-31 11:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-10 21:14 [Bug corefiles/11804] New: " jan dot kratochvil at redhat dot com
2010-07-10 21:15 ` [Bug corefiles/11804] " jan dot kratochvil at redhat dot com
2010-08-16 17:20 ` jan dot kratochvil at redhat dot com
2010-08-16 17:21 ` jan dot kratochvil at redhat dot com
2010-08-16 17:22 ` jan dot kratochvil at redhat dot com
2010-08-16 17:23 ` jan dot kratochvil at redhat dot com
2010-08-16 17:23 ` jan dot kratochvil at redhat dot com
2010-08-30  9:16 ` jan dot kratochvil at redhat dot com
2010-08-31 11:26 ` rguenth at gcc dot gnu dot org [this message]
2010-08-31 11:45 ` rguenth at gcc dot gnu dot org
2010-08-31 11:52 ` rguenth at gcc dot gnu dot org
2010-08-31 12:08 ` rguenth at gcc dot gnu dot org
2010-08-31 12:52 ` rguenth at gcc dot gnu dot org
2010-08-31 13:31 ` rguenth at gcc dot gnu dot org
2010-08-31 14:06 ` jan dot kratochvil at redhat dot com
2010-08-31 14:10 ` rguenth at gcc dot gnu dot org
2010-09-09 21:40 ` jan dot kratochvil at redhat dot com
     [not found] <bug-11804-4717@http.sourceware.org/bugzilla/>
2012-07-28  6:21 ` jan.kratochvil at redhat dot com
2012-07-28  7:07 ` jan.kratochvil at redhat dot com
2012-08-07 13:27 ` cvs-commit at gcc dot gnu.org
2012-08-07 13:28 ` jan.kratochvil at redhat dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100831112655.2522.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).