debug logging

[Rel]

Hi all,

Developing with jextract is a bit difficult:
- there is not too much debug logging, the "-Dlibclang.debug=true" enables certain logging but mostly for clang and not jextract itself. To find out what jextract is doing and trace it, is very difficult. It could be remidiated with running debug under IDE but it does not work well if you generate bindings for big "C" projects. Using "-Djextract.debug=true" as of today seems only prints more information during the exceptions but does not show what steps were taken before it
- Sometime you receive "Failed to parse /tmp/jextract$1721579888733730008.h:" message, when you try to see contents of /tmp/jextract$1721579888733730008.h to understand why it is failed the file is already deleted.
- no logging on what properties we pass to clang

Please let me know if I all this make sense or I am doing something wrong.

As part of my experiments on c++ side I integrated JUL to address these problems:

https://github.com/enatai/jextractcpp/commit/531f1d6183a53b0a1da0c18d7411f15bed7a23e3

If this seems useful for jextract I can send MR for it.

Regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/jextract-dev/attachments/20230820/f542ae3c/attachment.htm>