On Fri, 8 Apr 2022 11:11:29 GMT, Christian Hagedorn
wrote:
>> When printing the native stack trace on Linux (mostly done for hs_err
>> files), it only prints the method with its parameters and a relative offset
>> in the method:
>>
>> Stack: [0x7f6e01739000,0x7f6e0183a000],
On Fri, 13 May 2022 10:04:25 GMT, Magnus Ihse Bursie wrote:
>> I'm back to work again. I also had a look but could not find something on
>> Google, either. I then skimmed through the old GCC manuals. I found the
>> first occurrence of `-gdwarf-4` in the manual for GCC 4.5.4
>>
On Fri, 13 May 2022 08:43:35 GMT, Christian Hagedorn
wrote:
>> I'm googling around for some information about -gdwarf-4 but is mostly
>> coming up empty handed. :( I found
>> [this](https://www.phoronix.com/scan.php?page=news_item=GCC-11-DWARF-5-Possible-Default)
>> saying that dwarf-5
On Fri, 8 Apr 2022 11:11:29 GMT, Christian Hagedorn
wrote:
>> When printing the native stack trace on Linux (mostly done for hs_err
>> files), it only prints the method with its parameters and a relative offset
>> in the method:
>>
>> Stack: [0x7f6e01739000,0x7f6e0183a000],
On Fri, 8 Apr 2022 11:11:29 GMT, Christian Hagedorn
wrote:
>> When printing the native stack trace on Linux (mostly done for hs_err
>> files), it only prints the method with its parameters and a relative offset
>> in the method:
>>
>> Stack: [0x7f6e01739000,0x7f6e0183a000],
On Fri, 8 Apr 2022 13:34:03 GMT, Magnus Ihse Bursie wrote:
>> make/autoconf/flags-cflags.m4 line 116:
>>
>>> 114: fi
>>> 115:
>>> 116: CFLAGS_DEBUG_SYMBOLS="-g -gdwarf-4"
>>
>> We may need to guard this with a FLAGS_COMPILER_CHECK_ARGUMENTS. Perhaps it
>> should also be applied only
On Fri, 8 Apr 2022 13:02:00 GMT, Erik Joelsson wrote:
>> Christian Hagedorn has updated the pull request with a new target base due
>> to a merge or a rebase. The pull request now contains 60 commits:
>>
>> - Merge branch 'master' into JDK-8242181
>> - Fix build, add GCC flag gdwarf-4 to
On Fri, 8 Apr 2022 11:11:29 GMT, Christian Hagedorn
wrote:
>> When printing the native stack trace on Linux (mostly done for hs_err
>> files), it only prints the method with its parameters and a relative offset
>> in the method:
>>
>> Stack: [0x7f6e01739000,0x7f6e0183a000],
> When printing the native stack trace on Linux (mostly done for hs_err files),
> it only prints the method with its parameters and a relative offset in the
> method:
>
> Stack: [0x7f6e01739000,0x7f6e0183a000], sp=0x7f6e01838110, free
> space=1020k
> Native frames: (J=compiled
