Hi Patrick,
The problem can be in your doxyfile, could you show?
PS: If you want an example, the doxyfile that I'm using can be found
here<http://pastebin.com/37Xw24SV>.
You can generate a default one with "doxygen -g".
Best,
Rafael
2013/3/5 plafratt <plafr...@gmail.com>
> I have some code for a function for which Doxygen is generating a call
> graph.
> However, not all of the function calls are showing up in the call graph.
> Does anyone know what might be causing this? The code and the call graph
> are
> given below.
>
> For example, notice that the calls to "read_line" and "write_line" do not
> show up in the call graph.
>
> Thanks.
>
> ---
>
> <
> http://doxygen.10944.n7.nabble.com/file/n5734/classCache_a15b66e1df9e2676cea37fa050a9f86eb_cgraph.png
> >
>
> CacheBlockInfo*
> Cache::accessSingleLine(IntPtr addr, access_t access_type,
> Byte* buff, UInt32 bytes, SubsecondTime now)
> {
> //assert((buff == NULL) == (bytes == 0));
>
> IntPtr tag;
> UInt32 set_index;
> UInt32 line_index = -1;
> UInt32 block_offset;
>
> splitAddress(addr, tag, set_index, block_offset);
>
> CacheSet* set = m_sets[set_index];
> CacheBlockInfo* cache_block_info = set->find(tag, &line_index);
>
> if (cache_block_info == NULL)
> return NULL;
>
> if (access_type == LOAD)
> {
> // NOTE: assumes error occurs in memory. If we want to model bus
> errors, insert the error into buff instead
> if (m_fault_injector)
> m_fault_injector->preRead(addr, set_index * m_associativity +
> line_index, bytes, (Byte*)m_sets[set_index]->getDataPtr(line_index,
> block_offset), now);
>
> set->read_line(line_index, block_offset, buff, bytes);
> }
> else
> {
> set->write_line(line_index, block_offset, buff, bytes);
>
> // NOTE: assumes error occurs in memory. If we want to model bus
> errors, insert the error into buff instead
> if (m_fault_injector)
> m_fault_injector->postWrite(addr, set_index * m_associativity +
> line_index, bytes, (Byte*)m_sets[set_index]->getDataPtr(line_index,
> block_offset), now);
> }
>
> return cache_block_info;
> }
>
>
>
> --
> View this message in context:
> http://doxygen.10944.n7.nabble.com/Call-Graph-Incorrect-tp5734.html
> Sent from the Doxygen - Users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
> endpoint security space. For insight on selecting the right partner to
> tackle endpoint security challenges, access the full report.
> http://p.sf.net/sfu/symantec-dev2dev
> _______________________________________________
> Doxygen-users mailing list
> Doxygen-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/doxygen-users
>
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users
