From: "Neo Jia" <neojia@gmail.com>
To: tromey@redhat.com
Cc: "gdb ml" <gdb@sourceware.org>
Subject: Re: Source a python script to gdb plugin?
Date: Thu, 07 Aug 2008 17:01:00 -0000 [thread overview]
Message-ID: <5d649bdb0808071000rbe89429xc8b607f5822a60be@mail.gmail.com> (raw)
In-Reply-To: <m3ej50j538.fsf@fleche.redhat.com>
On Thu, Aug 7, 2008 at 7:02 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Neo" == Neo Jia <neojia@gmail.com> writes:
>
> Neo> I am going to source the following script through gdb plugin, but it
> Neo> doesn't work.
>
> Neo> Any suggestions?
>
> That isn't enough information. What platform is this? What version
> of Python are you using? How did it fail? Does it work with the
> ordinary python interpreter?
Linux x86_64. Python is 2.5.1.
> /opt/gdb_plugin/bin/gdb
GNU gdb (GDB) 6.8.50.20080716-cvs
Copyright (C) 2008 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 "x86_64-unknown-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
(gdb) source ./load_libc
/home/cjia/workareas/gdb_nvwatch/scripts/load_libc:3: Error in sourced command f
ile:
Undefined command: "from". Try "help".
(gdb)
execute the script out of the gdb.
> ./load_libc
100
Thanks,
Neo
>
> Tom
>
--
I would remember that if researchers were not ambitious
probably today we haven't the technology we are using!
next prev parent reply other threads:[~2008-08-07 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 7:40 Neo Jia
2008-08-07 14:03 ` Tom Tromey
2008-08-07 17:01 ` Neo Jia [this message]
2008-08-07 17:08 ` Paul Pluzhnikov
2008-08-07 17:13 ` Tom Tromey
2008-08-07 19:09 ` Neo Jia
2008-08-07 19:17 ` Tom Tromey
2008-08-07 19:18 ` Neo Jia
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=5d649bdb0808071000rbe89429xc8b607f5822a60be@mail.gmail.com \
--to=neojia@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