This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] Fix vDSO l_name for GDB's: Can't read pathname forload map: Input/output error.

From: Roland McGrath <roland at redhat dot com>
To: Daniel Jacobowitz <drow at false dot org>
Cc: Jan Kratochvil <jan dot kratochvil at redhat dot com>, libc-alpha at sourceware dot org
Date: Fri, 9 Oct 2009 11:03:11 -0700 (PDT)
Subject: Re: [patch] Fix vDSO l_name for GDB's: Can't read pathname forload map: Input/output error.
References: <20091004161706.GA27450@host0.dyn.jankratochvil.net><20091006063053.4E6101D@magilla.sf.frob.com><20091006085536.GA16155@host0.dyn.jankratochvil.net><20091008123440.GA19550@caradoc.them.org>

> FYI, I recently encountered a core file (from Solaris 10) where the
> name of ld.so was a pointer into ld.so's text segment... so this isn't
> always enough, but I think the best we can do there is warn.  I never
> did figure out how that situation came to pass.

Odd.  Ordinarily in GNU, it points to executable's PT_INTERP string.

References:
- [patch] Fix vDSO l_name for GDB's: Can't read pathname for load map:Input/output error.
  - From: Jan Kratochvil
- Re: [patch] Fix vDSO l_name for GDB's: Can't read pathname for load map:Input/output error.
  - From: Roland McGrath
- Re: [patch] Fix vDSO l_name for GDB's: Can't read pathname for loadmap: Input/output error.
  - From: Jan Kratochvil
- Re: [patch] Fix vDSO l_name for GDB's: Can't read pathname forload map: Input/output error.
  - From: Daniel Jacobowitz

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]