> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/9.0/developer-guide/idc/idc-api-reference/alphabetical-list-of-idc-functions/1253.md). # gen\_flow\_graph ``` Generate a flow chart GDL file outfile - output file name. GDL extension will be used title - graph title ea1 - beginning of the range to flow chart ea2 - end of the range to flow chart. if ea2 == BADADDR then ea1 is treated as an address within a function. That function will be flow charted. flags - combination of CHART_... constants success gen_flow_graph(string outfile, string title, long ea1, long ea2, long flags); #define CHART_PRINT_NAMES 0x1000 // print labels for each block? #define CHART_GEN_GDL 0x4000 // generate .gdl file (file extension is forced to .gdl) #define CHART_WINGRAPH 0x8000 // call wingraph32 to display the graph #define CHART_NOLIBFUNCS 0x0400 // don't include library functions in the graph ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.hex-rays.com/9.0/developer-guide/idc/idc-api-reference/alphabetical-list-of-idc-functions/1253.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.