Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c++ > #19144

Re: Tips to analyze a project with thousands of files

Show all headers | View raw

Thanks. So I am not the only one afraid of school bus.

I will learn to play with the cards I have.


"Jorgen Grahn" <grahn+nntp@snipabacken.se> wrote in message 
news:slrnk84lsu.1d3.grahn+nntp@frailea.sa.invalid...
> On Sat, 2012-10-20, Like Learn wrote:
>> My task is to analyze a legacy firmware project using Qualcomm MDM9X00
>> baseband chip with thousands of files (literally) to fix a bug. There is 
>> no
>> design documents about the project. The project is qriting in C++, halve 
>> of
>> them are commented in Doxygen format, while the other halve not. I don't
>> have the hardware to run the firmware or debugging. The only thing I have 
>> is
>> a list of debugging outputs of the printfs in firmware collected by the
>> client.
>
> The task is almost never to "analyze" something.  IME, it's only by
> doing actual useful work (changing a feature, doing internal changes
> or testing) that you can learn more about a large piece of code.
>
> I have often been in that situation. It's frustrating.  But you have
> to accept it:
>
> "I cannot understand all of this at once.  There are big parts I will
> probably never understand.  Most of this code is fit for
> thedailywtf.com. But I can fix this particular bug, and learn
> something while doing it, and the code will be better afterwards."
>
>> I spent one day today and even couldn't find out where the firmware 
>> starts.
>> Obviously it was not the main function. The comments are not in pure
>> English, frustrated. Any tip to find out the starting line of an ARM
>> project?
>
> Build it and look at the symbol table of the final image.  That is
> often a good supplement to looking at the source code.
>
> /Jorgen
>
> -- 
>  // Jorgen Grahn <grahn@  Oo  o.   .     .
> \X/     snipabacken.se>   O  o   . 



--- news://freenews.netfront.net/ - complaints: news@netfront.net ---

Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Tips to analyze a project with thousands of files "Like Learn" <like2learn@live.ca> - 2012-10-19 23:07 -0600
  Re: Tips to analyze a project with thousands of files Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-10-20 07:49 +0000
    Re: Tips to analyze a project with thousands of files "Like Learn" <like2learn@live.ca> - 2012-10-21 00:09 -0600
    Re: Tips to analyze a project with thousands of files Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-10-21 11:42 +0000
  Re: Tips to analyze a project with thousands of files Öö Tiib <ootiib@hot.ee> - 2012-10-20 09:14 -0700
    Re: Tips to analyze a project with thousands of files "Like Learn" <like2learn@live.ca> - 2012-10-21 00:12 -0600
  Re: Tips to analyze a project with thousands of files ctgqumgf@sharklasers.com - 2012-10-21 01:34 -0700
    Re: Tips to analyze a project with thousands of files Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-10-21 11:55 +0000
    Re: Tips to analyze a project with thousands of files "Like Learn" <like2learn@live.ca> - 2012-10-21 22:39 -0600
  Re: Tips to analyze a project with thousands of files Stuart <DerTopper@web.de> - 2012-10-23 13:00 +0200
  Re: Tips to analyze a project with thousands of files drew@furrfu.invalid (Drew Lawson) - 2012-10-24 15:33 +0000
  Re: Tips to analyze a project with thousands of files Werner <werasm@gmail.com> - 2012-10-24 09:29 -0700
    Re: Tips to analyze a project with thousands of files Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-10-25 20:44 +0000
  Re: Tips to analyze a project with thousands of files Luca Risolia <luca.risolia@studio.unibo.it> - 2012-10-24 22:42 +0200

csiph-web