From: vijay nag <vijunag@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb@sourceware.org
Subject: Fwd: vdso
Date: Fri, 05 Jul 2013 06:12:00 -0000 [thread overview]
Message-ID: <CAKhyrx_aX76L70XGWes+M2qsMu+=6E2UhO160YWCkxgGsL5XKA@mail.gmail.com> (raw)
In-Reply-To: <CAKhyrx8pAR9aKC1=-_HnwJ=ssb4B7LGUYM6CRqxY68xx+duprA@mail.gmail.com>
---------- Forwarded message ----------
From: vijay nag <vijunag@gmail.com>
Date: Fri, Jul 5, 2013 at 11:38 AM
Subject: Re: vdso
To: Jan Kratochvil <jan.kratochvil@redhat.com>
On Thu, Jul 4, 2013 at 11:40 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Wed, 03 Jul 2013 17:23:39 +0200, vijay nag wrote:
>> On Wednesday, July 3, 2013, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
>> > This warning is tracked as:
>> > http://sourceware.org/bugzilla/show_bug.cgi?id=14466
>> >
>> > and it is harmless, it should not affect functionality/symbols of GDB.
>> >
>> >
>> > Jan
>> >
>> Are you suggesting me that it could be a problem with glibc ?
>
> No.
>
>
> Jan
The function linux_proc_xfer_partial() is returning result zero when
trying to pread64 /proc/<pid>/mem and errno is set to -EIO.
Does that mean kernel doesn't support pread64 on /proc/xxx/mem files ?
gdb) l
4392
4393 /* We could keep this file open and cache it - possibly one per
4394 thread. That requires some juggling, but is even faster. */
4395 sprintf (filename, "/proc/%d/mem", PIDGET (inferior_ptid));
4396 fd = open (filename, O_RDONLY | O_LARGEFILE);
4397 if (fd == -1)
4398 return 0;
4399
4400 /* If pread64 is available, use it. It's faster if the kernel
4401 supports it (only one syscall), and it's 64-bit safe even on
(gdb) l
4402 32-bit platforms (for instance, SPARC debugging a SPARC64
4403 application). */
4404 #ifdef HAVE_PREAD64
4405 if (pread64 (fd, readbuf, len, offset) != len)
4406 #else
4407 if (lseek (fd, offset, SEEK_SET) == -1 || read (fd, readbuf,
len) != len)
4408 #endif
4409 ret = 0;
4410 else
4411 ret = len;
(gdb) p *__errno_location()
$18 = 5
(gdb)
next prev parent reply other threads:[~2013-07-05 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 8:34 vdso vijay nag
2013-07-03 8:42 ` vdso Jan Kratochvil
2013-07-03 9:15 ` vdso vijay nag
2013-07-03 9:03 ` vdso Jan Kratochvil
2013-07-03 9:06 ` vdso vijay nag
[not found] ` <CAKhyrx_9fSc5wMaXaX76bFOPJbuVFttDNJ-YDa28wz5obJHQyQ@mail.gmail.com>
2013-07-03 14:49 ` vdso Jan Kratochvil
[not found] ` <20130703144857.GA27367@host2.jankratochvil.net>
[not found] ` <CAKhyrx8GCE7bYeZe9gnNT_aZN74oM--kd_oZr1+cjqt67oOzVQ@mail.gmail.com>
[not found] ` <20130704061052.GA19661@host2.jankratochvil.net>
[not found] ` <CAKhyrx8pAR9aKC1=-_HnwJ=ssb4B7LGUYM6CRqxY68xx+duprA@mail.gmail.com>
2013-07-05 6:12 ` vijay nag [this message]
[not found] ` <20130705184238.GA661@host2.jankratochvil.net>
2013-07-08 6:50 ` Fwd: vdso vijay nag
2013-07-08 8:47 ` Jan Kratochvil
2013-07-08 9:12 ` vijay nag
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='CAKhyrx_aX76L70XGWes+M2qsMu+=6E2UhO160YWCkxgGsL5XKA@mail.gmail.com' \
--to=vijunag@gmail.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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