Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: vijay nag <vijunag@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Fwd: vdso
Date: Mon, 08 Jul 2013 09:12:00 -0000	[thread overview]
Message-ID: <CAKhyrx_QWb+xMg-Bbn850GF6ZKHYFQ6uwsP52_ugONf8jt2teQ@mail.gmail.com> (raw)
In-Reply-To: <20130708084723.GA25829@host2.jankratochvil.net>

On Mon, Jul 8, 2013 at 2:17 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Mon, 08 Jul 2013 08:50:49 +0200, vijay nag wrote:
>> Breakpoint 1, linux_proc_xfer_partial (ops=0x8499230, object=TARGET_OBJECT_MEMORY, annex=0x0, readbuf=0xbffff250 "\r", writebuf=0x0, offset=4294967296, len=4294959104)
>>     at linux-nat.c:4386
>> 4386    if (object != TARGET_OBJECT_MEMORY || !readbuf)
>> (gdb) p /x offset
>> $3 = 0xffffe000
>> (gdb) p /x len
>> $4 = 0x34
>
> offset and len in the first line correspond to offset 0x100000000
> and len 0xffffe000 resp.  So I do not see the values you printed from GDB
> below.
>
> This is general debugging of GDB, it no longer belongs to this list.
> You should best file it to GDB Bugzilla and try to provide reproducibility
> information.
>
>
> There seems to be some 32->64bit extension problem (0x100000000).  Isn't the
> GDB built for x86_64 target while you run it for i386 target?  This sure
> should work but there may be some issues.  Try to build 32-bit host GDB as
> troubleshooting:
>         CFLAGS=-m32 ./configure i386-unknown-linux-gnu
> But this is already rather for the Bugzilla.
>
>
> Jan
I've built 32 bit gdb configured for i686-pc-linux-gnu and my kernel
too is 32 bit one.

gdb
GNU gdb (GDB) 7.5
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.

uname -a
Linux 2.6.18-myos-v2-38059-deb #1 SMP Sun Apr 3 01:48:20 EDT 2011 i686 GNU/Linux

Are you saying that gdb is miscalculating offset of vdso ?


      reply	other threads:[~2013-07-08  9: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                   ` Fwd: vdso vijay nag
     [not found]                     ` <20130705184238.GA661@host2.jankratochvil.net>
2013-07-08  6:50                       ` vijay nag
2013-07-08  8:47                         ` Jan Kratochvil
2013-07-08  9:12                           ` vijay nag [this message]

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_QWb+xMg-Bbn850GF6ZKHYFQ6uwsP52_ugONf8jt2teQ@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