Re: [fvwmorg/fvwm] 1d38f7: !!! Start work on replacing the parsing in __execu...

On Wed, Oct 26, 2016 at 01:45:46PM +0100, Thomas Adam wrote: > On Wed, Oct 26, 2016 at 02:21:57PM +0200, Dominik Vogt wrote: > > First of all I hope I'll be able to find the crash caused by a free of a > > string that is still > > used, then experiment with it to see whether a step by step

Separate or common project infrastructure fvwm v2/v3.

This is important enough to warrant a separate discussion thread. On Wed, Oct 26, 2016 at 01:45:46PM +0100, Thomas Adam wrote: > Oh, and the point of a separate repo still stands, in my eyes. You might > think it moot, or even an unnecessary point, but I feel it's a very important > one. It

Re: [fvwmorg/fvwm] 1d38f7: !!! Start work on replacing the parsing in __execu...

On Thu, Oct 27, 2016 at 12:58:14AM +0100, Dominik Vogt wrote: > Ah. Technically, the branch is probably as good as it will get. > Any changed to the "stdint.h" branch can easily be backported, but > that may not be necessary. > > However, if we agree on this becoming the "long time stable" >

Re: [fvwmorg/fvwm] 1d38f7: !!! Start work on replacing the parsing in __execu...

On Thu, Oct 27, 2016 at 12:41:03AM +0100, Dominik Vogt wrote: > On Thu, Oct 27, 2016 at 12:15:36AM +0100, Thomas Adam wrote: > > On Wed, Oct 26, 2016 at 11:45:53PM +0100, Dominik Vogt wrote: > > > Maybe, maybe not. This work only changes the inner structure of > > > the parser yet and has few

Re: [fvwmorg/fvwm] 1d38f7: !!! Start work on replacing the parsing in __execu...

On Wed, Oct 26, 2016 at 11:45:53PM +0100, Dominik Vogt wrote: > Maybe, maybe not. This work only changes the inner structure of > the parser yet and has few user visible changes (some rarely > triggered quoting issues). Any chance we could at least get that done though? It seems daft not to.

Re: [fvwmorg/fvwm] 5b3250: Fix gettext write to read only string; fix warning...

On 10/25/2016 06:38 PM, Dominik Vogt wrote: Right. A solution must disable the warnings on any compilers and versions the developers use, and not break compilation anywhere. The way I generally do it is check for the compiler, and then define a macro for gcc and for clang using those

Re: [fvwmorg/fvwm] 1d38f7: !!! Start work on replacing the parsing in __execu...

On Wed, Oct 26, 2016 at 12:04:46PM +0200, Dominik Vogt wrote: > > On Tue, Oct 25, 2016 at 03:41:45PM -0700, GitHub wrote: > > > Branch: refs/heads/dv/new-parser-2 > ... > > > > I ported all of this over before here: > > > > https://github.com/fvwmorg/fvwm/tree/new-parser > > > > You should

Re: [fvwmorg/fvwm] 1d38f7: !!! Start work on replacing the parsing in __execu...

On Tue, Oct 25, 2016 at 03:41:45PM -0700, GitHub wrote: > Branch: refs/heads/dv/new-parser-2 > Home: https://github.com/fvwmorg/fvwm > Commit: 1d38f7a2727f28f1817e1c951bc07267002d2006 > > https://github.com/fvwmorg/fvwm/commit/1d38f7a2727f28f1817e1c951bc07267002d2006 > Author:

Re: [fvwmorg/fvwm] 1d38f7: !!! Start work on replacing the parsing in __execu...

On Wed, Oct 26, 2016 at 02:21:57PM +0200, Dominik Vogt wrote: > First of all I hope I'll be able to find the crash caused by a free of a > string that is still > used, then experiment with it to see whether a step by step replacement of > the old > parser is feasible while keeping the old parser

Re: [fvwmorg/fvwm] 1d38f7: !!! Start work on replacing the parsing in __execu...

> On Tue, Oct 25, 2016 at 03:41:45PM -0700, GitHub wrote: > > Branch: refs/heads/dv/new-parser-2 ... > > I ported all of this over before here: > > https://github.com/fvwmorg/fvwm/tree/new-parser > > You should just rebase that against master, and use that if it's any use? This new branch is

Re: [fvwmorg/fvwm] 1d38f7: !!! Start work on replacing the parsing in __execu...

> Gesendet: Mittwoch, 26. Oktober 2016 um 12:06 Uhr > Von: "Thomas Adam" > An: "Dominik Vogt" > Cc: fvwm-workers@fvwm.org > Betreff: Re: [fvwmorg/fvwm] 1d38f7: !!! Start work on replacing the parsing > in __execu... > > On Wed, Oct 26, 2016 at 12:04:46PM

Re: [fvwmorg/fvwm] 5b3250: Fix gettext write to read only string; fix warning...

On Wed, Oct 26, 2016 at 08:40:02AM +0200, Florian Schmidt wrote: > On 10/25/2016 06:38 PM, Dominik Vogt wrote: > >Right. A solution must disable the warnings on any compilers and > >versions the developers use, and not break compilation anywhere. > > The way I generally do it is check for the