Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
We need more information
1. Build debug build with "-O0" and "-fno-omit-framepointer" so we can analyze "bactrace" by symbolizing it using debug info. Otherwise we got random source code lines, because actual code is optimized by compiler and not mapped one to one (binary to source).
2. Think how we can dump "sql query" for debug build, at least we can dump Execution Plan which is available in ExeMgr.
3. How about other information like memory RAM memory available, process memory map.
Attachments
Issue Links
- blocks
-
MCOL-5265 TupleHashJoin::segregateJoiners double throws causing SIGABRT
- Closed