This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: varobj/1956: argc is always 0
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 5 Jun 2005 02:38:01 -0000
- Subject: Re: varobj/1956: argc is always 0
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR varobj/1956; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: kernel-stuff@comcast.net
Cc: gdb-gnats@sources.redhat.com
Subject: Re: varobj/1956: argc is always 0
Date: Sat, 4 Jun 2005 22:31:17 -0400
On Sun, Jun 05, 2005 at 01:49:17AM -0000, kernel-stuff@comcast.net wrote:
> (gdb) r 1 2 3 4
> Starting program: /home/parag/qt-x11-opensource-4.0.0-rc1-snapshot-20050604/examples/layouts/flowlayout/flowlayout 1 2 3 4
> [Thread debugging using libthread_db enabled]
> [New Thread 46912531523776 (LWP 13010)]
> [Switching to Thread 46912531523776 (LWP 13010)]
>
> Breakpoint 1, main (argc=0, argv=0x7fffffffee38) at main.cpp:34
> 34 {
> (gdb) print argc
> $1=0
This usually means that your compiler has generated incorrect
information about the end of the prologue or the location of argc.
It's not GDB's fault.
--
Daniel Jacobowitz
CodeSourcery, LLC