Git development
 help / color / mirror / Atom feed
From: Mahesh Pujari <pujarimahesh_kumar@yahoo.com>
To: David Kastrup <dak@gnu.org>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git compile with debug symbols
Date: Tue, 4 Mar 2014 22:27:00 -0800 (PST)	[thread overview]
Message-ID: <1394000820.21154.YahooMailNeo@web162905.mail.bf1.yahoo.com> (raw)
In-Reply-To: <8761ntj4ny.fsf@fencepost.gnu.org>

Hello all,
 Thanks for replying back, figured out (offcourse had to search in net) that 'gdb' version I had was 6.7.1 (OS Ubuntu 12.04 LST), not sure how I got this. Then I upgraded gdb to version 7.4-2012.04 and things got going.


thanks,
mpujari


On Tuesday, March 4, 2014 10:13 PM, David Kastrup <dak@gnu.org> wrote:
Mahesh Pujari <pujarimahesh_kumar@yahoo.com> writes:

> Thanks David for the reply. I think I need to do more ground work of
> going through how to use gdb.
> Basically I am java programmer and I was trying out to debug git
> source using eclipse CDT and as we do in java, I was trying out to set
> break point but failed with errors as "No line 396 in file "help.c"".
> And using gdb too I end up with same error.
>
> # (gdb) break help.c:396
> # No line 396 in file "help.c".
>
>
> Am I missing something.

There is just no line 396 known to gdb.  It seems like you are
indicating a function header.  That's not code.  Either take the
function _name_ rather than a line number (that's usually most reliable)
or take the first line of actual code.


-- 
David Kastrup

  reply	other threads:[~2014-03-05  6:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-04 15:46 git compile with debug symbols Mahesh Pujari
2014-03-04 15:53 ` David Kastrup
2014-03-04 16:03   ` Matthieu Moy
2014-03-04 16:33     ` Mahesh Pujari
2014-03-04 16:43       ` David Kastrup
2014-03-05  6:27         ` Mahesh Pujari [this message]
2014-03-04 16:00 ` karthik nayak
2014-03-04 17:53 ` Tanay Abhra

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=1394000820.21154.YahooMailNeo@web162905.mail.bf1.yahoo.com \
    --to=pujarimahesh_kumar@yahoo.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=dak@gnu.org \
    --cc=git@vger.kernel.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