Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Yogesh Mundada <yogesh.mundada@gmail.com>
To: tromey@redhat.com
Cc: gdb@sourceware.org
Subject: Re: gdb python setup problem
Date: Tue, 23 Mar 2010 06:26:00 -0000	[thread overview]
Message-ID: <1957618c1003222326j41f82412l9ab77295568975cc@mail.gmail.com> (raw)
In-Reply-To: <m3ocil39r4.fsf@fleche.redhat.com>

I followed instructions from http://sourceware.org/gdb/wiki/PythonGdb.
But I don't think I am getting the correct branch.
Here are commands for your reference:

yogesh@destiny:~$ git clone git://sourceware.org/git/archer.git
git: /usr/local/lib/libidn.so.11: no version information available
(required by /usr/lib/libcurl-gnutls.so.4)
Initialized empty Git repository in /home/yogesh/archer/.git/
git: /usr/local/lib/libidn.so.11: no version information available
(required by /usr/lib/libcurl-gnutls.so.4)
git-index-pack: /usr/local/lib/libidn.so.11: no version information
available (required by /usr/lib/libcurl-gnutls.so.4)
remote: Counting objects: 309735, done.
remote: Compressing objects: 100% (57761/57761), done.
Receiving objects: 100% (309735/309735), 116.01 MiB | 758 KiB/s, done.
remote: Total 309735 (delta 245181), reused 309056 (delta 244653)
Resolving deltas: 100% (245181/245181), done.
Checking out files: 100% (7324/7324), done.
yogesh@destiny:~$
yogesh@destiny:~$ ls -ltr
total 708
-rw-r--r--  1 yogesh yogesh 668436 2010-03-08 09:46
ws7_replay_linux_technote.pdf
-rw-r--r--  1 yogesh yogesh     63 2010-03-17 17:43 gp-cont.py
drwxr-xr-x  3 yogesh yogesh   4096 2010-03-22 23:48 vmware
drwxr-xr-x  4 yogesh yogesh   4096 2010-03-23 01:07 Downloads
drwxr-xr-x  2 yogesh yogesh   4096 2010-03-23 01:12 Desktop
drwxr-xr-x 16 yogesh yogesh   4096 2010-03-23 01:15 archer
yogesh@destiny:~$
yogesh@destiny:~$ cd archer; git checkout --track -b python
origin/archer-tromey-python
git: /usr/local/lib/libidn.so.11: no version information available
(required by /usr/lib/libcurl-gnutls.so.4)
Branch python set up to track remote branch archer-tromey-python from origin.
Switched to a new branch 'python'
yogesh@destiny:~/archer$

I think that libidn related messages are harmless. I've the blog
entries from "The Cliffs of Inanity" and I really want to try this gdb
scripting feature. What can I do to checkout the correct branch?

Any help is greatly appreciated.

On Thu, Mar 18, 2010 at 11:55 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Yogesh" == Yogesh Mundada <yogesh.mundada@gmail.com> writes:
>
> A few things that the other responses didn't cover...
>
> Yogesh> #!/home/yogesh/build/gdb/gdb -P
>
> We haven't submitted the -P patch yet.
>
> Yogesh> Then I got the source code from archer-tromey-python branch as
> Yogesh> mentioned in http://sourceware.org/gdb/wiki/PythonGdb. I compiled that
> Yogesh> source code but still it did not have any -P option for python
> Yogesh> scripting.
>
> Make sure you are on the right branch -- archer-tromey-python.
>
> Tom
>


  reply	other threads:[~2010-03-23  6:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17 21:19 Yogesh Mundada
2010-03-17 21:27 ` Zi Shen Lim
2010-03-17 21:52   ` Joel Brobecker
2010-03-18 15:55 ` Tom Tromey
2010-03-23  6:26   ` Yogesh Mundada [this message]
2010-03-23 15:31     ` Tom Tromey
2010-03-23 15:42       ` Yogesh Mundada

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=1957618c1003222326j41f82412l9ab77295568975cc@mail.gmail.com \
    --to=yogesh.mundada@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=tromey@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