Thread overview |
---|
September 13, 2019 Name change weird | ||||
---|---|---|---|---|
| ||||
I edited one of my librarys and found my programs crashing. At first, I couldn't find what was wrong but used GitHub to review my changes. I found an enum[0] that had a name change - that my programs weren't even using. All the change that was from 'enum g_Draw {text, input}' to 'enum g_draw {text, input}' (just changed the D to lowercase). I fixed it by making the D uppercase again - D Programming Language (code-d) marks it as not the right style. https://github.com/joelcnz [0] JecLib - base.d |
September 13, 2019 Re: Name change weird | ||||
---|---|---|---|---|
| ||||
Posted in reply to Joel | On Friday, 13 September 2019 at 05:39:06 UTC, Joel wrote:
> I edited one of my librarys and found my programs crashing. At first, I couldn't find what was wrong but used GitHub to review my changes. I found an enum[0] that had a name change - that my programs weren't even using. All the change that was from 'enum g_Draw {text, input}' to 'enum g_draw {text, input}' (just changed the D to lowercase). I fixed it by making the D uppercase again - D Programming Language (code-d) marks it as not the right style.
>
> https://github.com/joelcnz
>
> [0] JecLib - base.d
Actually, forget about the above. It's still crashing in run time.
jex(2204,0x700005356000) malloc: Incorrect checksum for freed object 0x7ffc9368cdf8: probably modified after being freed.
Corrupt value: 0x7ffc9368000d
jex(2204,0x700005356000) malloc: *** set a breakpoint in malloc_error_break to debug
Program exited with code -6
Also get:
Program exited with code -11
Having this problem since documenting (eg /// discription) some of my code.
|
September 13, 2019 Re: Name change weird | ||||
---|---|---|---|---|
| ||||
Posted in reply to Joel | On Friday, 13 September 2019 at 05:57:53 UTC, Joel wrote:
> On Friday, 13 September 2019 at 05:39:06 UTC, Joel wrote:
>> [...]
>
> Actually, forget about the above. It's still crashing in run time.
>
> jex(2204,0x700005356000) malloc: Incorrect checksum for freed object 0x7ffc9368cdf8: probably modified after being freed.
> Corrupt value: 0x7ffc9368000d
> jex(2204,0x700005356000) malloc: *** set a breakpoint in malloc_error_break to debug
> Program exited with code -6
>
> Also get:
> Program exited with code -11
>
> Having this problem since documenting (eg /// discription) some of my code.
I'm using DSFML 2.1.1 on macOS 10.14.6 DMD 2.087.1 (home brew). I have upgraded macOS recently - I don't know if that's it. I haven't been able to get a much newer version DSFML to work.
|
September 13, 2019 Re: Name change weird | ||||
---|---|---|---|---|
| ||||
Posted in reply to Joel | On Friday, 13 September 2019 at 06:07:57 UTC, Joel wrote:
> On Friday, 13 September 2019 at 05:57:53 UTC, Joel wrote:
>> On Friday, 13 September 2019 at 05:39:06 UTC, Joel wrote:
>>> [...]
>>
>> Actually, forget about the above. It's still crashing in run time.
>>
>> jex(2204,0x700005356000) malloc: Incorrect checksum for freed object 0x7ffc9368cdf8: probably modified after being freed.
>> Corrupt value: 0x7ffc9368000d
>> jex(2204,0x700005356000) malloc: *** set a breakpoint in malloc_error_break to debug
>> Program exited with code -6
>>
>> Also get:
>> Program exited with code -11
>>
>> Having this problem since documenting (eg /// discription) some of my code.
>
> I'm using DSFML 2.1.1 on macOS 10.14.6 DMD 2.087.1 (home brew). I have upgraded macOS recently - I don't know if that's it. I haven't been able to get a much newer version DSFML to work.
I think it's the macOS update. Programs that ran before, now crash, not my DLangUI ones. Seems to be with input handling using the DSFML library, I have a program that has graphics and audio, but not looking for keyboard input - that runs properly.
|
September 13, 2019 Re: Name change weird | ||||
---|---|---|---|---|
| ||||
Posted in reply to Joel | Maybe you upgraded SFML and now binding doesn't match? |
September 13, 2019 Re: Name change weird | ||||
---|---|---|---|---|
| ||||
Posted in reply to Kagamin | On Friday, 13 September 2019 at 09:54:58 UTC, Kagamin wrote:
> Maybe you upgraded SFML and now binding doesn't match?
I didn't touch SFML dylibs. I guess I could try recompling them. It's a bit late here in New Zealand, though.
|
September 13, 2019 Re: Name change weird | ||||
---|---|---|---|---|
| ||||
Posted in reply to Joel | On Friday, 13 September 2019 at 10:02:35 UTC, Joel wrote:
> On Friday, 13 September 2019 at 09:54:58 UTC, Kagamin wrote:
>> Maybe you upgraded SFML and now binding doesn't match?
>
> I didn't touch SFML dylibs. I guess I could try recompling them. It's a bit late here in New Zealand, though.
I tried recompiling and it didn't work at first. But compiled by recloning with git. Still have the same fatal problem. My platform game plays a popping sound over and over (which would go once at program launch before).
|
September 13, 2019 Re: Name change weird | ||||
---|---|---|---|---|
| ||||
Posted in reply to Joel | On Fri, Sep 13, 2019 at 05:57:53AM +0000, Joel via Digitalmars-d-learn wrote: [...] > jex(2204,0x700005356000) malloc: Incorrect checksum for freed object > 0x7ffc9368cdf8: probably modified after being freed. > Corrupt value: 0x7ffc9368000d > jex(2204,0x700005356000) malloc: *** set a breakpoint in malloc_error_break > to debug > Program exited with code -6 > > Also get: > Program exited with code -11 [...] This looks like a memory corruption bug. Possibly it was masked before, but due to recent changes in the compiler / druntime, the bug got exposed. T -- Nobody is perfect. I am Nobody. -- pepoluan, GKC forum |
September 13, 2019 Re: Name change weird | ||||
---|---|---|---|---|
| ||||
Posted in reply to H. S. Teoh | On Friday, 13 September 2019 at 12:20:48 UTC, H. S. Teoh wrote:
> On Fri, Sep 13, 2019 at 05:57:53AM +0000, Joel via Digitalmars-d-learn wrote: [...]
>> jex(2204,0x700005356000) malloc: Incorrect checksum for freed object
>> 0x7ffc9368cdf8: probably modified after being freed.
>> Corrupt value: 0x7ffc9368000d
>> jex(2204,0x700005356000) malloc: *** set a breakpoint in malloc_error_break
>> to debug
>> Program exited with code -6
>>
>> Also get:
>> Program exited with code -11
> [...]
>
> This looks like a memory corruption bug. Possibly it was masked before, but due to recent changes in the compiler / druntime, the bug got exposed.
>
>
> T
Yeah, input handling would crash in the past, too, but own if you switched away from the program and started doing something else.
|
Copyright © 1999-2021 by the D Language Foundation