From: Ken Brown <kbrown@cornell.edu>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: aneesh.kumar@linux.vnet.ibm.com, emacs-devel@gnu.org
Subject: Re: gdb-create-source-file-list and gdb-mi.el
Date: Fri, 25 Nov 2011 17:28:25 -0500 [thread overview]
Message-ID: <4ED01689.1060108@cornell.edu> (raw)
In-Reply-To: <1322031913.8188.4.camel@totara.tehura.co.nz>
On 11/23/2011 2:05 AM, Nick Roberts wrote:
>> gdb-mi.el does the below
>>
>> ;; find source file and compilation directory here
>> (gdb-input
>> ; Needs GDB 6.2 onwards.
>> (list "-file-list-exec-source-files" 'gdb-get-source-file-list))
>> (if gdb-create-source-file-list
>> (gdb-input
>> ; Needs GDB 6.0 onwards.
>> (list "-file-list-exec-source-file" 'gdb-get-source-file)))
>
>> Don't we need to make sure the the "-file-list-exec-source-files" also
>> come withing the gdb-crate-source-file-list check ?. Current gdb with
>> linux kernel vmlinux takes so much time to give me the prompt.
>
> Yes it looks like I made a mistake. The if clause should be around the first gdb-input.
>
> I don't know the status of the freeze so I've not committed this change.
As long as you're looking at gdb-mi.el problems, there have been several
other bugs reported:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9853
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9858
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9878
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9944
Could you take a look at those also?
Ken
next prev parent reply other threads:[~2011-11-25 22:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 7:05 Re:gdb-create-source-file-list and gdb-mi.el Nick Roberts
2011-11-25 22:28 ` Ken Brown [this message]
2011-11-26 7:00 ` gdb-create-source-file-list " Chong Yidong
2011-11-29 7:52 ` Aneesh Kumar K.V
2011-11-29 8:45 ` Nick Roberts
2011-11-29 15:29 ` gdb-create-source-file-list " Ken Brown
2011-11-29 18:46 ` Stefan Monnier
2011-11-30 3:32 ` Ken Brown
-- strict thread matches above, loose matches on Subject: below --
2011-11-18 10:29 Aneesh Kumar K.V
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=4ED01689.1060108@cornell.edu \
--to=kbrown@cornell.edu \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.