Re: setup crashing - fixed?

Re: setup crashing - fixed?

[Michael A Chase]

----- Original Message -----
From: "Gary R. Van Sickle" <g.r.vansickle@worldnet.att.net>
To: "Corinna Vinschen" <cygwin-apps@cygwin.com>
Sent: Monday, January 28, 2002 20:24
Subject: RE: setup crashing - fixed?

> -----Original Message-----
> From: cygwin-apps-owner@cygwin.com
> [mailto:cygwin-apps-owner@cygwin.com]On Behalf Of Corinna Vinschen
> > . . .
> > By explicitely expressing my wish to change the state by pointy clicky
> > somewhere.  Honestly, think of the current "test" installation of
> > tetex and texmf which is > 30 Megs.  If the user actually chooses
> > to go back to the "curr" version, it's his/her choice.  If that
> > happens while the user actually just wanted to update to the latest
> > bazzoo-3.3-8 package it's pretty annoying.
>
> SOMEBODY ***FINALLY*** PORTED BAZZOO 3.3 TO CYGWIN?!?!  WHY DIDN'T YOU
GUYS TELL
> ME!?!?!?!?
>
> Oh man the guys at work are gonna go WILD when I tell 'em!

I think that was a typo.  The latest I see is still 3.2. :}b
--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.

Re: setup crashing - fixed?

[Christopher Faylor]

On Mon, Jan 28, 2002 at 08:44:23PM -0800, Michael A Chase wrote:
>----- Original Message -----
>From: "Gary R. Van Sickle" <g.r.vansickle@worldnet.att.net>
>To: "Corinna Vinschen" <cygwin-apps@cygwin.com>
>Sent: Monday, January 28, 2002 20:24
>Subject: RE: setup crashing - fixed?
>
>> -----Original Message-----
>>From: cygwin-apps-owner@cygwin.com
>>[mailto:cygwin-apps-owner@cygwin.com]On Behalf Of Corinna Vinschen
>>>.  .  .  By explicitely expressing my wish to change the state by
>>>pointy clicky somewhere.  Honestly, think of the current "test"
>>>installation of tetex and texmf which is > 30 Megs.  If the user
>>>actually chooses to go back to the "curr" version, it's his/her choice.
>>>If that happens while the user actually just wanted to update to the
>>>latest bazzoo-3.3-8 package it's pretty annoying.
>>
>>SOMEBODY ***FINALLY*** PORTED BAZZOO 3.3 TO CYGWIN?!?! WHY DIDN'T YOU
>>GUYS TELL ME!?!?!?!?
>>
>>Oh man the guys at work are gonna go WILD when I tell 'em!
>
>I think that was a typo.  The latest I see is still 3.2.  :}b

Look in the 'alpha' directory.  I don't know why it is marked as alpha.
It seems pretty stable to me.

Or, at least it doesn't seem to delete files any more often than bazzoo
3.1 did.  According to the bazzoo mailing list, there is a simple way
to disallow this "feature" but I've never managed to make it work.  One
of these days, I have to look at the source and see exactly what I'm
doing wrong.

I'm embarrassed to admit that I haven't actually tried this under
Windows yet but I can't imagine that bazzoo would work any differently
under Cygwin than it does under Linux.  It doesn't use any special stuff
besides unix domain sockets, vfork, and setuid.

I'm glad to see that there are other bazzoo users here.  This is a not
too small but still relatively unpowerful package suitable for both the
expert and the non-novice alike.

cgf

Re: setup crashing - fixed?

[Corinna Vinschen]

On Tue, Jan 29, 2002 at 12:14:57AM -0500, Chris Faylor wrote:
> On Mon, Jan 28, 2002 at 08:44:23PM -0800, Michael A Chase wrote:
> >----- Original Message -----
> >From: "Gary R. Van Sickle" <g.r.vansickle@worldnet.att.net>
> >To: "Corinna Vinschen" <cygwin-apps@cygwin.com>
> >Sent: Monday, January 28, 2002 20:24
> >Subject: RE: setup crashing - fixed?
> >
> >> -----Original Message-----
> >>From: cygwin-apps-owner@cygwin.com
> >>[mailto:cygwin-apps-owner@cygwin.com]On Behalf Of Corinna Vinschen
> >>>.  .  .  By explicitely expressing my wish to change the state by
> >>>pointy clicky somewhere.  Honestly, think of the current "test"
> >>>installation of tetex and texmf which is > 30 Megs.  If the user
> >>>actually chooses to go back to the "curr" version, it's his/her choice.
> >>>If that happens while the user actually just wanted to update to the
> >>>latest bazzoo-3.3-8 package it's pretty annoying.
> >>
> >>SOMEBODY ***FINALLY*** PORTED BAZZOO 3.3 TO CYGWIN?!?! WHY DIDN'T YOU
> >>GUYS TELL ME!?!?!?!?
> >>
> >>Oh man the guys at work are gonna go WILD when I tell 'em!
> >
> >I think that was a typo.  The latest I see is still 3.2.  :}b
> 
> Look in the 'alpha' directory.  I don't know why it is marked as alpha.
> It seems pretty stable to me.

But be *extremly* careful using 3.3!  It's in an early development
stage and it's marked as "pretty useless" by it's developers.
Actually they are discussing to renumber that release to 0.9.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

RE: setup crashing - fixed?

[Gary R. Van Sickle]

> -----Original Message-----
> From: cygwin-apps-owner@cygwin.com
> [mailto:cygwin-apps-owner@cygwin.com]On Behalf Of Corinna Vinschen

[snip]

> But be *extremly* careful using 3.3!  It's in an early development
> stage and it's marked as "pretty useless" by it's developers.
> Actually they are discussing to renumber that release to 0.9.

Oh man, but just to have bazzoo on Windows, after all these years... I'm
throwing all caution to the wind!  I just hope I have enough memory and disk
space.

BTW, who's the Cygwin bazzoo maintainer?

--
Gary R. Van Sickle
Brewer.  Patriot.

Re: setup crashing - fixed?

[Earnie Boyd]

"Gary R. Van Sickle" wrote:
> 
> BTW, who's the Cygwin bazzoo maintainer?
> 

Don't you remember?  You said that you would maintain it.

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: setup crashing - fixed?

[Corinna Vinschen]

On Wed, Jan 30, 2002 at 06:59:49AM -0500, Earnie Boyd wrote:
> "Gary R. Van Sickle" wrote:
> > 
> > BTW, who's the Cygwin bazzoo maintainer?
> > 
> 
> Don't you remember?  You said that you would maintain it.
> 
> Earnie.

If not... hmm... I heard rumors that perhaps... L. Gerstner is looking
for a new hobby in 2003, you know...

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

RE: setup crashing - fixed?

[Gary R. Van Sickle]

> -----Original Message-----
> From: cygwin-apps-owner@cygwin.com
> [mailto:cygwin-apps-owner@cygwin.com]On Behalf Of Corinna Vinschen

[snip]

>
> By explicitely expressing my wish to change the state by pointy clicky
> somewhere.  Honestly, think of the current "test" installation of
> tetex and texmf which is > 30 Megs.  If the user actually chooses
> to go back to the "curr" version, it's his/her choice.  If that
> happens while the user actually just wanted to update to the latest
> bazzoo-3.3-8 package it's pretty annoying.
>

SOMEBODY ***FINALLY*** PORTED BAZZOO 3.3 TO CYGWIN?!?!  WHY DIDN'T YOU GUYS TELL
ME!?!?!?!?

Oh man the guys at work are gonna go WILD when I tell 'em!

--
Gary R. Van Sickle
Brewer.  Patriot.

Re: setup crashing - fixed?

[Robert Collins]

----- Original Message -----
From: "Corinna Vinschen" <cygwin-apps@cygwin.com>
>
> By explicitely expressing my wish to change the state by pointy clicky
> somewhere.  Honestly, think of the current "test" installation of
> tetex and texmf which is > 30 Megs.  If the user actually chooses
> to go back to the "curr" version, it's his/her choice.  If that
> happens while the user actually just wanted to update to the latest
> bazzoo-3.3-8 package it's pretty annoying.

Which is the reason for the existence of the 'partial' screen - so that
userscan see what is going to be done before it happens.

Likewise if you downgrade a package, or hold it back, setup will try to
upgrade it every time. We need more information about the users desire -
to allow 'Holding' a package, or setting one package to 'test' and all
the others to 'curr', but I've not had time to code that yet.

Rob

Re: setup crashing - fixed?

[Corinna Vinschen]

On Tue, Jan 29, 2002 at 09:29:02AM +1100, Robert Collins wrote:
> 
> ===
> ----- Original Message -----
> From: "Corinna Vinschen" <cygwin-apps@cygwin.com>
> > > Corinna, can you CVS update and try a fresh build?
> >
> > It works now for me, too.  Thanks!
> 
> Good! Whew.
> 
> > Btw., the current setup behaviour is somewhat dangerous(?) or
> > unexpected(?) in one point.
> 
> Go
> 
> > If a package is available in current and in test version and a user
> > has the test version installed, the default behaviour of setup is
> > to reinstall the current version.  Shouldn't the default behaviour
> > in that case keep the already installed test version?
> 
> If does that, how does the user indicate that they want everything back
> to normal?

By explicitely expressing my wish to change the state by pointy clicky
somewhere.  Honestly, think of the current "test" installation of
tetex and texmf which is > 30 Megs.  If the user actually chooses
to go back to the "curr" version, it's his/her choice.  If that
happens while the user actually just wanted to update to the latest
bazzoo-3.3-8 package it's pretty annoying.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

Re: setup crashing - fixed?

[Robert Collins]

===
----- Original Message -----
From: "Corinna Vinschen" <cygwin-apps@cygwin.com>
> > Corinna, can you CVS update and try a fresh build?
>
> It works now for me, too.  Thanks!

Good! Whew.

> Btw., the current setup behaviour is somewhat dangerous(?) or
> unexpected(?) in one point.

Go

> If a package is available in current and in test version and a user
> has the test version installed, the default behaviour of setup is
> to reinstall the current version.  Shouldn't the default behaviour
> in that case keep the already installed test version?

If does that, how does the user indicate that they want everything back
to normal?

Rob

Re: setup crashing - fixed?

[Robert Collins]

===
----- Original Message -----
From: "Corinna Vinschen" <cygwin-apps@cygwin.com>
> > Corinna, can you CVS update and try a fresh build?
>
> It works now for me, too.  Thanks!

Good! Whew.

> Btw., the current setup behaviour is somewhat dangerous(?) or
> unexpected(?) in one point.

Go

> If a package is available in current and in test version and a user
> has the test version installed, the default behaviour of setup is
> to reinstall the current version.  Shouldn't the default behaviour
> in that case keep the already installed test version?

If does that, how does the user indicate that they want everything back
to normal?

Rob

Re: setup crashing - fixed?

[Corinna Vinschen]

On Sun, Jan 27, 2002 at 05:41:00PM +1100, Robert Collins wrote:
> Right, I think I found the cause. At least I can successfully download
> from *every* available site, and before I had repeatable problems doing
> that.
> 
> Corinna, can you CVS update and try a fresh build?

It works now for me, too.  Thanks!

Btw., the current setup behaviour is somewhat dangerous(?) or
unexpected(?) in one point.

If a package is available in current and in test version and a user
has the test version installed, the default behaviour of setup is
to reinstall the current version.  Shouldn't the default behaviour
in that case keep the already installed test version?

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

RE: setup crashing - fixed?

[Gary R. Van Sickle]

> -----Original Message-----
> From: cygwin-apps-owner@cygwin.com
> [mailto:cygwin-apps-owner@cygwin.com]On Behalf Of Robert Collins
> Sent: Sunday, January 27, 2002 12:41 AM
> To: cygwin-apps@sources.redhat.com
> Subject: setup crashing - fixed?
> 
> 
> Right, I think I found the cause. At least I can successfully download
> from *every* available site, and before I had repeatable problems doing
> that.
>

Appears to be working for me now.

-- 
Gary R. Van Sickle
Brewer.  Patriot.  
 

Re: setup crashing - fixed?

[Robert Collins]

===
----- Original Message -----
From: "Michael A Chase" <mchase@ix.netcom.com>
> I hope you moved the '+ 1' outside the strlen() as well.

Yes - that was the point - moving it outside, on it's own, didn't fix
the heap corruption. Moving it outside AND moving the constructor body
to be non-inlinable did.

Rob

Re: setup crashing - fixed?

[Michael A Chase]

----- Original Message ----- 
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: <cygwin-apps@sources.redhat.com>
Sent: Saturday, January 26, 2002 22:41
Subject: setup crashing - fixed?


> Right, I think I found the cause. At least I can successfully download
> from *every* available site, and before I had repeatable problems doing
> that.
> 
> Corinna, can you CVS update and try a fresh build?
> 
> I found a bug that could have caused the issue:
> 
> site (char const *newkey)
> {
>   key = new char[strlen (newkey + 1)];
>                                ^^^^^
>     strcpy (key, newkey);
> };
> 
> However, fixing that DID NOT fix the problem (although I had isolated
> the fault to this constructor by means of replacement new and new[]
> calls using HeapAlloc, combined with HeapValidate().)
> 
> Moving the constructor body out of the header fixed the problem. I don't
> have time to generate a testcase, but if anyone does have time, I'm sure
> the gcc team would appreciate knowing about this. The fault occured when
> that constructor was called from a template instantiation of list.h.

I hope you moved the '+ 1' outside the strlen() as well.
-- 
Mac :})
** I normally forward private questions to the appropriate mail list. **
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.

setup crashing - fixed?

[Robert Collins]

Right, I think I found the cause. At least I can successfully download
from *every* available site, and before I had repeatable problems doing
that.

Corinna, can you CVS update and try a fresh build?

I found a bug that could have caused the issue:

site (char const *newkey)
{
  key = new char[strlen (newkey + 1)];
                               ^^^^^
    strcpy (key, newkey);
};

However, fixing that DID NOT fix the problem (although I had isolated
the fault to this constructor by means of replacement new and new[]
calls using HeapAlloc, combined with HeapValidate().)

Moving the constructor body out of the header fixed the problem. I don't
have time to generate a testcase, but if anyone does have time, I'm sure
the gcc team would appreciate knowing about this. The fault occured when
that constructor was called from a template instantiation of list.h.

Rob