I've chosen to work on Mago, with the following goals:

-Porting it to D first and foremost to make code maintenance and expansion easier in the future.
-Add better support for Win32-COFF (there's a few more bugs compared to Win32-OMF in my experience) and Win64-COFF. As I read COFF32 needs some manual installation, which will be made easier by either a Powershell script, or even a custom installer, the latter might branch out on its own project.
-Fix some general bugs, like the non-working -break-insert -f.
-Add some simple GUI for Mago-mi instead of just the GDB compatible text interface.
-Make it to work better with LDC if possible.

If I'll have time after the main milestones, I might add other functions besides the bug fixes, such as a memory editor, ability to debug programs and codes written in C and other languages for interoperability.

Additionally you can help me to work on my college thesis. I still haven't chosen my subject matter, but it'll be either my graphics engine "PixelPerfectEngine", my compression library "lzbacon", or this if it's allowed. I need a mentor/consultant (the latter is what I got for the translation of the word "konzulens"), your main job is to help me out a bit.

On Sun, 26 Aug 2018 at 09:50, solidstate1991 via Digitalmars-d <digitalmars-d@puremagic.com> wrote:
>
> I've chosen to work on Mago, with the following goals:
>
> -Porting it to D first and foremost to make code maintenance and
> expansion easier in the future.
> -Add better support for Win32-COFF (there's a few more bugs
> compared to Win32-OMF in my experience) and Win64-COFF. As I read
> COFF32 needs some manual installation, which will be made easier
> by either a Powershell script, or even a custom installer, the
> latter might branch out on its own project.
> -Fix some general bugs, like the non-working -break-insert -f.
> -Add some simple GUI for Mago-mi instead of just the GDB
> compatible text interface.
> -Make it to work better with LDC if possible.
>
> If I'll have time after the main milestones, I might add other functions besides the bug fixes, such as a memory editor, ability to debug programs and codes written in C and other languages for interoperability.
>
> Additionally you can help me to work on my college thesis. I still haven't chosen my subject matter, but it'll be either my graphics engine "PixelPerfectEngine", my compression library "lzbacon", or this if it's allowed. I need a mentor/consultant (the latter is what I got for the translation of the word "konzulens"), your main job is to help me out a bit.

I think one of the only people qualified to help you is Rainer Schutze. I think he knows the details of Mago better than anyone.

Incidentally, I use Mago exclusively and I'm not sure I have any of
these problems you're speaking of.
Mixed D/C++ debugging is working well in VS. Memory editing is also
working fine...?
Top of my wish-list would be a way to evaluate pure
functions/properties while stepping as if variables.

On Monday, 27 August 2018 at 07:45:03 UTC, Manu wrote:

>
> I think one of the only people qualified to help you is Rainer Schutze. I think he knows the details of Mago better than anyone.

Rainer is unable to participate in SAoC as a mentor this time around. So we're looking for anyone with the time and the willingness to step up.

On Sunday, 26 August 2018 at 16:47:47 UTC, solidstate1991 wrote:
> I've chosen to work on Mago, with the following goals:
>
> -Porting it to D first and foremost to make code maintenance and expansion easier in the future.
> -Add better support for Win32-COFF (there's a few more bugs compared to Win32-OMF in my experience) and Win64-COFF. As I read COFF32 needs some manual installation, which will be made easier by either a Powershell script, or even a custom installer, the latter might branch out on its own project.
> -Fix some general bugs, like the non-working -break-insert -f.
> -Add some simple GUI for Mago-mi instead of just the GDB compatible text interface.
> -Make it to work better with LDC if possible.
>
> [...]

I guess I could help you out with coff.

generating it is not the problem but linking it on windows currently requires the MS linker.
which may not be desired.
then again ... I think binutils do support coff as well.

On Monday, 27 August 2018 at 20:47:08 UTC, Stefam Koch wrote:
> generating it is not the problem but linking it on windows currently requires the MS linker.

Is that true, though? DMD ships with LLD these days. — David

On 28/08/2018 9:32 AM, David Nadlinger wrote:
> On Monday, 27 August 2018 at 20:47:08 UTC, Stefam Koch wrote:
>> generating it is not the problem but linking it on windows currently requires the MS linker.
> 
> Is that true, though? DMD ships with LLD these days. — David
> 

And is 100% experimental on both LLD and on the D front.

On Monday, 27 August 2018 at 21:32:10 UTC, David Nadlinger wrote:
> On Monday, 27 August 2018 at 20:47:08 UTC, Stefam Koch wrote:
>> generating it is not the problem but linking it on windows currently requires the MS linker.
>
> Is that true, though? DMD ships with LLD these days. — David

Really ... I am so out of touch these days.

On Monday, 27 August 2018 at 20:47:08 UTC, Stefam Koch wrote:
>
> I guess I could help you out with coff.
>
> generating it is not the problem but linking it on windows currently requires the MS linker.
> which may not be desired.
> then again ... I think binutils do support coff as well.

I might need you as a mentor. Currently I'm thinking out of the milestones, I probably can fully convert Mago to D by the end of September, in October I'll work on getting the COFF64 support at the same level as 32 bit ones, November and December will be spent with developing a GUI and bug fixes.