From: Keith Seitz <keiths@redhat.com>
To: "\"María de los A. Vázquez\"" <mvazquez@micromint.com>
Cc: insight <insight@sourceware.org>
Subject: Re: Initialization Commands
Date: Fri, 30 Oct 2009 18:00:00 -0000 [thread overview]
Message-ID: <4AEB29B0.6080009@redhat.com> (raw)
In-Reply-To: <3ECE384639D045ABA34B78C72EE7B4FA@HELP3>
On 10/30/2009 10:52 AM, MarÃa de los A. Vázquez wrote:
> I'm new with gdb and insight. I'm loading Insight from Code::Blocks to
> use it as my debbuger but I'm having problems with the Initialization
> Commands and .gdbinit file. When I run the debugger (Insight) it didn't
> recognize the initialization commands under Debugger settings
> (Code::Blocks) neither the init file (.gdbinit). Instead I always need
> to enter the commands manually so I don't know what I'm doing wrong??
> Where does I need to declared the .gdbinit file so it recognize it???
> Any help will be useful for me!!! Thanks.
I don't know anything about Code::Blocks, but it sounds to me like they
are starting up gdb/insight using the "-nx" option, which suppresses
reading .gdbinit.
Where is .gdbinit? Gdb looks in two places: $HOME and $PWD, i.e., your
home directory and the current directory. If .gdbinit is not in $HOME, I
would put it there and see if that works.
> BTW
> I only have two declarations on the .gdbinit file:
> "target remote localhost:3333"
> "load"
If you go to the Target Settings Dialog, you can have insight do this
for you automatically when you click the Run button. Of course, if
Code::Blocks is passing "-nx" to gdb/insight, insight won't read your
preferences file, anyway. But if you're like me and typically type at a
console window, this won't help you.
Keith
next prev parent reply other threads:[~2009-10-30 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 17:51 María de los A. Vázquez
2009-10-30 18:00 ` Keith Seitz [this message]
2009-11-02 20:20 ` María de los A. Vázquez
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=4AEB29B0.6080009@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=mvazquez@micromint.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).