From: "Luo Yi" <firingme@gmail.com>
To: gdb@sourceware.org
Subject: Re: How can I define the breakpoint-commands in my gdbinit file
Date: Thu, 14 Dec 2006 02:01:00 -0000 [thread overview]
Message-ID: <77d8667c0612131801g34de0db7xded2053720115525@mail.gmail.com> (raw)
In-Reply-To: <20061214015351.GA5203@nevyn.them.org>
luoyi@slack$ cat ~/.gdbinit
define mybp
b main
commands
silent
printf "eax = %x\n", $eax
end
end
luoyi@slack$ gdb a.out
GNU gdb 6.5
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as
"i486-slackware-linux".../home/luoyi/.gdbinit:7: Error in sourced
command file:
This command cannot be used at the top level.
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(gdb) mybp
Breakpoint 1 at 0x8048440
Quit <<------------------ gdb stop here! after Ctrl+C, it go on with this
(gdb)
2006/12/14, Daniel Jacobowitz <drow@false.org>:
> On Thu, Dec 14, 2006 at 09:51:19AM +0800, Luo Yi wrote:
> > How can I define the breakpoint-commands in my gdbinit file ?
> >
> > define b1
> > b *0x805d3bf
> > commands
> > silent
> > printf "ne, eax = %x\n", $eax
> > end <<< ------------
> > end
> >
> > the commands need a end instruction which can't appear in the middle
> > of the gdbinit file.
>
> It should work fine. Are you using the latest GDB?
> --
> Daniel Jacobowitz
> CodeSourcery
>
next prev parent reply other threads:[~2006-12-14 2:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 1:51 Luo Yi
2006-12-14 1:54 ` Daniel Jacobowitz
2006-12-14 2:01 ` Luo Yi [this message]
2006-12-14 3:10 ` Daniel Jacobowitz
2006-12-14 4:27 ` Eli Zaretskii
2006-12-14 5:02 ` Luo Yi
2006-12-14 21:10 ` Eli Zaretskii
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=77d8667c0612131801g34de0db7xded2053720115525@mail.gmail.com \
--to=firingme@gmail.com \
--cc=gdb@sourceware.org \
/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