unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Denis Golovan <denis.golovan@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: gdb-show-main disappeared...
Date: Mon, 7 Jul 2008 09:25:19 +1200	[thread overview]
Message-ID: <18545.14399.150496.103105@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20080706160543.GB6949@dencomp.local>

 > > That sounds like a different problem.  How do you mean "it doesn't work"?
 > 
 >   Doesn't show main function and can't be called from mini-buffer (I think
 >   command-line below is called so)

gdb-show-main is a variable, not a function, so you can't do
M-x gdb-show-main.  From the mini-buffer, gou need to do
M-x set-variable<RET>
Set variable: t (say)


 > > The principles of bug reporting are not specific to Emacs.  See the node
 > > "Reporting Bugs" in the Emacs manual. Can you explain what the symptoms
 > > are and exactly how to reproduce it?
 > 
 >   Well, it's easy - try to build emacs from svn source, build any program
 > with debug info and M-x gdb. Next is all we discussing. BTW, gdb-ui DOES
 > contain gdb-show-main, I checked.

What happens if you set a breakpoint at main and type "run" in the GUD buffer?
If the source doesn't appear in a buffer it probably means that you haven't
compiled with debug information (-g option).

-- 
Nick                                           http://www.inet.net.nz/~nickrob




  reply	other threads:[~2008-07-06 21:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-02 17:38 gdb-show-main disappeared Denis Golovan
2008-07-03 21:29 ` Nick Roberts
     [not found]   ` <20080704145511.GA8325@dencomp.local>
2008-07-04 22:36     ` Nick Roberts
2008-07-06 16:05       ` Denis Golovan
2008-07-06 21:25         ` Nick Roberts [this message]
2008-07-09 12:02           ` Denis Golovan
  -- strict thread matches above, loose matches on Subject: below --
2008-07-02 19:34 Denis Golovan
2008-07-02 19:39 Denis Golovan

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18545.14399.150496.103105@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=denis.golovan@gmail.com \
    --cc=help-gnu-emacs@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).