rdmd main.d leads to Segmentation fault
Timoses
timosesu at gmail.com
Sun Jan 28 22:02:11 UTC 2018
On Saturday, 27 January 2018 at 21:04:07 UTC, Kagamin wrote:
> On Friday, 26 January 2018 at 22:40:29 UTC, Timoses wrote:
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x00432e04 in _d_dso_registry ()
>> (gdb) bt
>> #0 0x00432e04 in _d_dso_registry ()
>> #1 0x00431c63 in ?? ()
>> #2 0x0045c08b in __libc_csu_init ()
>> #3 0xb7d8e206 in __libc_start_main (main=0x431c24 <main>,
>> argc=1, argv=0xbffff784,
>> init=0x45c040 <__libc_csu_init>, fini=0x45c0a0
>> <__libc_csu_fini>,
>> rtld_fini=0xb7feb080 <_dl_fini>, stack_end=0xbffff77c) at
>> ../csu/libc-start.c:247
>> #4 0x004315c1 in _start ()
>>
>>
>>
>> Any ideas?
>
> What `disas` command shows at the point of failure?
How would I do that?
$ (gdb) info line main
No line number information available for address 0x431c24 <main>
$ (gdb) info line 0x431c24
Function "0x431c24" not defined.
?
More information about the Digitalmars-d-learn
mailing list