Ilya

Thanks for reaching out! There may be changes in the newer Linux kernel versions that are not yet supported by dwarf2json. What error(s) are you seeing? Also, I think the...

Thanks for your suggestion. Unfortunately, it is not known how many structures need to be processed from a DWARF file ahead of time. Thus, outputting the progress for `dwarf2json` operation...

Hi @avizack18, Thanks for your question. The recommendation is to have 8GB of RAM: https://github.com/volatilityfoundation/dwarf2json/blob/master/README.md?plain=1#L27. You do not need to have a large swap file or use one at all....

Hi @jgru, Thanks for trying out the branch and providing feedback. The error is indicative on an issue with parsing the DWARF in `module.ko`. We are actively working on creating...

Hi @jgru, I'm not able to reproduce the reported error and can generate an ISF with the files you provided. I'm likely using a different `reference.json` than you are, but...

Hi @ikelos, You are raising valid points. I agree that it would be useful to differentiate ISF files created with debug kernels and those created with module.ko method. The ISF...

Hi @jgru, Thanks for this additional information. It looks like I had a small code change in my local repo that hasn't been committed. It explains the difference in behavior...

@ikelos, It's worth discussing. The current interface to `dwarf2json` is very generic. It receives a list of dwarf files and the client specifies for each whether to extract types, symbols,...

> I'm not sure creating a second file would help since someone could end up using only one and we'd not get the data we needed. I think we would...

Hi @jdlovato, Thank you for the feature request! Being able to generate a profile without a full debug kernel is a useful feature. In addition to `system.map` and `module.dwarf`, a...