Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Lee <backrev@yahoo.com>
Cc: gdb@sources.redhat.com
Subject: Re: arc argv problems
Date: Fri, 25 Aug 2006 21:37:00 -0000	[thread overview]
Message-ID: <20060825213718.GA21431@nevyn.them.org> (raw)
In-Reply-To: <20060825213013.94568.qmail@web55607.mail.re4.yahoo.com>

On Fri, Aug 25, 2006 at 02:30:13PM -0700, Lee wrote:
> I am doing all of this on linux gdb build 
> gdb-6.5.50.20060823
> 
> I dumbed down my script for demo purposes here
> I even downloaded some sample .gdbinit files and they
> did not work either
> 
> I am not sure if this is a bug, or user error

Your GDB appears to be very, very broken.  I get completely different
results using the same gdbinit, which look correct.

> edircpr:/gdb/gdb-6.5.50.20060823/gdb # vi ~/.gdbinit
> edircpr:/gdb/gdb-6.5.50.20060823/gdb # gdb
> GNU gdb 6.4
> Copyright 2005 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.

You appear to have edited out your platform.  Where are you running
this?
> I have also tried using $ARGC etc, but I think the
> correct one to use is $argc $argv

$argc and $arg0 and $arg1.

> Also I have not found any good scripting references
> specific to gdb.  While it is very similar to other
> things, there are things that work special like printf
> that are close but not the same.

It's all in the GDB manual.  Search for $argc.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2006-08-25 21:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-25 21:30 Lee
2006-08-25 21:37 ` Daniel Jacobowitz [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=20060825213718.GA21431@nevyn.them.org \
    --to=drow@false.org \
    --cc=backrev@yahoo.com \
    --cc=gdb@sources.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