lucas.ferreira likes this.
  • hello @HSoni202357 (Community Member)​ 

     

    It seems that you couldn't compile/built the application correctly. I recommend you review packaging accordinly to language: Package your code | Veracode Docs

     

    depending of language that you are using, you must be compiled with debug symbols. With that, scanner could show you the files and line number of flaw

    Expand Post
  • Hi @HSoni202357 (Community Member)​ ,

     

    This is mostly because the debug symbol were not enabled for compile. Make sure that you submit a debug build with debug symbols enabled. For e.g For a .Net app, please ensure that the .DLL file have .PDB file also included.

     

    As Lucas correctly suggested, please follow the compilation and packaging guidelines.

     

    If you still have questions I would recommend you schedule a consultation call to discuss.

    You can check out this knowledge article (https://community.veracode.com/s/article/How-to-schedule-a-consultation-call) on how to schedule a consultation call with us.

    Regards,

    Kashif

    Expand Post
    • HSoni202357 (Community Member)

      I had published code with debug symbol enabled and also the zip folder contains the .pdb file. But still reports contains some of them without source file and linenumber.

      • Hi, The scan needs to reviewed for its pre-scan warnings. I recommend you scheduling a consultation if you like.

Topics (3)

No articles found
Loading

Ask the Community

Get answers, share a use case, discuss your favorite features, or get input from the community.