You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Quanlong Huang (Jira)" <ji...@apache.org> on 2022/07/21 05:24:00 UTC
[jira] [Commented] (IMPALA-3164) Debugging support for codegen'd code
[ https://issues.apache.org/jira/browse/IMPALA-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17569273#comment-17569273 ]
Quanlong Huang commented on IMPALA-3164:
----------------------------------------
FWIW, a paper about debugging codegen: "On Another Level: How to Debug Compiling Query Engines" [http://www.db.in.tum.de/~kersten/codegen_debugger.pdf]
> Debugging support for codegen'd code
> ------------------------------------
>
> Key: IMPALA-3164
> URL: https://issues.apache.org/jira/browse/IMPALA-3164
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 2.6.0
> Reporter: Tim Armstrong
> Priority: Minor
> Labels: codegen, supportability
>
> After the switch to MCJIT and LLVM 3.7.0 (IMPALA-775) it should be possible to debug codegened code, since MCJIT can emit DWARF debug info and gdb versions 7 and higher support finding the debug info for LLVM's jitted code. (Ref http://llvm.org/docs/DebuggingJITedCode.html) There are a few things to do to make sure that this works well:
> * Get LLVM to emit cross-compiled code with debug symbols for the debug build
> * Work out how to add debug symbols to IRBuilder-generated code (maybe with the DebugIR LLVM pass).
> * Test that it actually works
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org