From: Andrew Wozniak <awozniak@mc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Patch to show address definition based on file
Date: Thu, 20 Oct 2005 16:27:21 -0400 [thread overview]
Message-ID: <4357FDA9.5070002@mc.com> (raw)
In-Reply-To: <4A062D477D842B4C8FC48EA5AF2D41F201527F6A@us-bv-m23.global.tektronix.net>
cscope alway looks in the current directory for the cscope.out file. If
you cd into another directory, use this to specify the cscope.out path:
cscope -f <path>/cscope.out
BTW, this is all OFF-TOPIC. see http://cscope.sourceforge.net for docs!
atul.sabharwal at exgate.tek.com wrote:
> I did that. Then I did cscope -b -R -u -q to enable a fast recursive index
> file generation in the top directory. Now I go to cpu/mpc8xx and search
> For the typedef bd_t from that directory & cannot find it. There
> Are some environment varibles e.g. $HOME or $SOURCEDIRS and it does not
> work. Even define a CSCOPE_DIR variable in the main.c to change cwd to this
> Directory but no quick solution. Unless its some user error on my part:)
>
> -----Original Message-----
> From: Frank [mailto:frannk_m1 at yahoo.com]
> Sent: Wednesday, October 19, 2005 7:54 PM
> To: Sabharwal, Atul; u-boot-users at lists.sourceforge.net
> Subject: Re: [U-Boot-Users] Patch to show address definition based on
> file/line number with e xtra flags in the nm command
>
> at the top level directory:
> find . -name "*.[sSch]" -print >cscope.files
>
>
> --- atul.sabharwal at exgate.tek.com wrote:
>
>> This is a nit but instead of tracing code using cscope/ctags
>> or fgrep, this
>> method
>> Makes code tracing lot quicker. Unless you have an IDE :)
>>
>> I have used cscope but have not been able to search symbols at
>> a top level
>> Directory from a directory N level deep. Any tips
>> appreciated.
>>
>>
>> --- /login/asabharw/lxhome/u-boot-1.1.3/Makefile 2005-08-13
>> 16:53:35.000000000 -0700
>> +++ Makefile 2005-10-17 18:59:37.000000000 -0700
>> @@ -194,7 +194,7 @@
>> \( -name CVS -prune \) -o \( -name '*.[ch]' -print
>> \)`
>>
>> System.map: u-boot
>> - @$(NM) $< | \
>> + $(NM) -A -l $< | \
>> grep -v '\(compiled\)\|\(\.o$$\)\|\( [aUw]
>> \)\|\(\.\.ng$$\)\|\(LASH[RL]DI\)' | \
>> sort > System.map
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by:
>> Power Architecture Resource Center: Free content, downloads,
>> discussions,
>> and more. http://solutions.newsforge.com/ibmarch.tmpl
>> _______________________________________________
>> U-Boot-Users mailing list
>> U-Boot-Users at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/u-boot-users
>>
>
>
>
>
> __________________________________
> Yahoo! Music Unlimited
> Access over 1 million songs. Try it free.
> http://music.yahoo.com/unlimited/
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
>
prev parent reply other threads:[~2005-10-20 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 18:24 [U-Boot-Users] Patch to show address definition based on file /line number with e xtra flags in the nm command atul.sabharwal at exgate.tek.com
2005-10-20 20:27 ` Andrew Wozniak [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=4357FDA9.5070002@mc.com \
--to=awozniak@mc.com \
--cc=u-boot@lists.denx.de \
/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 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.