Re: cvsup broken on amd64?

On 10/06/2011 01:41, Thomas Mueller wrote: > Anyway, from what I read, csup is better, and I think I can use the same > supfile and same server that I would use for cvsup? Yes. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth

Re: cvsup broken on amd64?

On Wed, Oct 05, 2011 at 03:21:45PM -0700, David O'Brien wrote: > On Fri, Sep 09, 2011 at 06:00:02PM +0300, Kostik Belousov wrote: > > --- libs/m3core/src/thread/POSIX/ThreadPosix.m3.orig2011-09-09 > > 17:58:12.867431639 +0300 > > +++ libs/m3core/src/thread/POSIX/ThreadPosix.m3 2011-09-

Re: cvsup broken on amd64?

> cvsup is a port, so you would need to install that to have cvsup. csup > and cvsup are totally different code bases in different languages. > (csup is C and cvsup is Modula-3.) You probably want to install cvsup > as a package as installing the port also requires building all of the > Modula-3 co

Re: cvsup broken on amd64?

On Fri, Sep 09, 2011 at 06:00:02PM +0300, Kostik Belousov wrote: > --- libs/m3core/src/thread/POSIX/ThreadPosix.m3.orig 2011-09-09 > 17:58:12.867431639 +0300 > +++ libs/m3core/src/thread/POSIX/ThreadPosix.m3 2011-09-09 > 17:58:30.380428486 +0300 > @@ -180,7 +180,7 @@ >pausedThreads : T

Re: cvsup broken on amd64?

On Wed, Oct 5, 2011 at 1:34 AM, Thomas Mueller wrote: >> Hi all, > >> I've committed this to -head. > >> I'd appreciate it if csup users would give this a thorough testing and >> report back to the list with results. >> I won't submit this as a merge candidate this to stable/9 without a >> whole l

Re: cvsup broken on amd64?

> Hi all, > I've committed this to -head. > I'd appreciate it if csup users would give this a thorough testing and > report back to the list with results. > I won't submit this as a merge candidate this to stable/9 without a > whole lot of testing. :) > Thanks, > Adrian I am now in 9.0-

Re: cvsup broken on amd64?

Hi all, I've committed this to -head. I'd appreciate it if csup users would give this a thorough testing and report back to the list with results. I won't submit this as a merge candidate this to stable/9 without a whole lot of testing. :) Thanks, Adrian ___

Re: cvsup broken on amd64?

On Tue, Oct 4, 2011 at 2:19 AM, Adrian Chadd wrote: > On 4 October 2011 05:53, Maxime Henrion wrote: > >> Great, that's a relief. I knew the pthread library was free to wake a >> thread up even if it hadn't been signaled, which is why one always has >> to call pthread_cond_wait() inside of a whil

Re: cvsup broken on amd64?

On 4 October 2011 05:53, Maxime Henrion wrote: > Great, that's a relief. I knew the pthread library was free to wake a > thread up even if it hadn't been signaled, which is why one always has > to call pthread_cond_wait() inside of a while() loop checking for the > condition, but wasn't sure abou

Re: cvsup broken on amd64?

On Mon, Oct 3, 2011 at 11:30 PM, Jilles Tjoelker wrote: > On Mon, Oct 03, 2011 at 06:15:41PM +0200, Maxime Henrion wrote: >> Knowing all that, what's happening seems quite clear. If >> fixups_close() is called while there was still fixup requests pending, >> those should be processed by the detail

Re: cvsup broken on amd64?

On Mon, Oct 03, 2011 at 06:15:41PM +0200, Maxime Henrion wrote: > Knowing all that, what's happening seems quite clear. If > fixups_close() is called while there was still fixup requests pending, > those should be processed by the detailer thread before it returns. > Subsequent fixups_get() call sh

Re: cvsup broken on amd64?

On Mon, Sep 19, 2011 at 8:26 AM, Adrian Chadd wrote: > 2011/9/19 Alexander Zagrebin : > >> I've tried this patch. Now csup "hangs" before handling fixups. >> So there is no message "Applying fixups..." at all. > > Wow. Hm. Where's the author when one needs them.. Well that's quite a strange coinc

Re: cvsup broken on amd64?

2011/9/19 Alexander Zagrebin : > I've tried this patch. Now csup "hangs" before handling fixups. > So there is no message "Applying fixups..." at all. Wow. Hm. Where's the author when one needs them.. Adrian ___ freebsd-current@freebsd.org mailing lis

RE: cvsup broken on amd64?

Hi! > So I've taken a look at the csup source. > > The problem here is the updater thread setting the "closed" state > (fixups_closed()) before calling updater_batch() again to handle > fixups. > > Checking for size != 0 at that point may not be valid at the list size > may actually be 0 for a s

Re: cvsup broken on amd64?

On Sun, Sep 18, 2011 at 02:46:24PM +0200, Oliver Lehmann wrote: > > Kostik Belousov wrote: > > >Did you saw the message with the patch for tzcode I mailed to you ? > > Mmmh... no didn't reached my mailbox - can you resend it please? See the "Segfault in libthr.so on 9.0-BETA2 (with stunnel FW

Re: cvsup broken on amd64?

Kostik Belousov wrote: Did you saw the message with the patch for tzcode I mailed to you ? Mmmh... no didn't reached my mailbox - can you resend it please? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/free

Re: cvsup broken on amd64?

Ah, you're the one with the csup problem. Would you mind trying csup again, and if it doesn't work, try this patch: Index: updater.c === --- updater.c (revision 224905) +++ updater.c (working copy) @@ -240,9 +240,9 @@ *

Re: cvsup broken on amd64?

On Sun, Sep 18, 2011 at 12:22:53PM +0200, Oliver Lehmann wrote: > > Adrian Chadd wrote: > > >So I've taken a look at the csup source. > > > >[...] > > > >What about this patch: > > > >[...] > > > >Oliver, would you please try that? > > I have a problem with cvsup, not csup - Alexander mentioned

Re: cvsup broken on amd64?

Adrian Chadd wrote: So I've taken a look at the csup source. [...] What about this patch: [...] Oliver, would you please try that? I have a problem with cvsup, not csup - Alexander mentioned a csup problem. ___ freebsd-current@freebsd.org maili

Re: cvsup broken on amd64?

Hi, So I've taken a look at the csup source. The problem here is the updater thread setting the "closed" state (fixups_closed()) before calling updater_batch() again to handle fixups. Checking for size != 0 at that point may not be valid at the list size may actually be 0 for a short period of t

Re: cvsup broken on amd64?

On Thu, Sep 15, 2011 at 9:30 AM, Garrett Cooper wrote: > On Thu, Sep 15, 2011 at 8:19 AM, Adrian Chadd wrote: >> On 15 September 2011 18:05, Mark Linimon wrote: Usually rather quite later than sooner. >>> >>> A perfect opportunity for src committers to dive in and make a >>> difference :-)

Re: cvsup broken on amd64?

On Thu, Sep 15, 2011 at 8:19 AM, Adrian Chadd wrote: > On 15 September 2011 18:05, Mark Linimon wrote: >>> Usually rather quite later than sooner. >> >> A perfect opportunity for src committers to dive in and make a >> difference :-) > > I hate you. :) > > Ok. Some third person test/verify that t

Re: cvsup broken on amd64?

On 15 September 2011 18:05, Mark Linimon wrote: >> Usually rather quite later than sooner. > > A perfect opportunity for src committers to dive in and make a > difference :-) I hate you. :) Ok. Some third person test/verify that this patch (a) does what it's supposed to do, and (b) is correct, a

Re: cvsup broken on amd64?

> Usually rather quite later than sooner. A perfect opportunity for src committers to dive in and make a difference :-) mcl ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any m

Re: cvsup broken on amd64?

on 15/09/2011 12:16 Alexander Zagrebin said the following: >> Pester the maintainer? > > I've thought that if an opened PR exists, then it have to be > reviewed sooner or later... > Usually rather quite later than sooner. There are about 5000 non-ports PRs and there are only a few dozen active

RE: cvsup broken on amd64?

> Pester the maintainer? I've thought that if an opened PR exists, then it have to be reviewed sooner or later... -- Alexander Zagrebin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubsc

Re: cvsup broken on amd64?

On Wed, Sep 14, 2011 at 11:19 PM, Adrian Chadd wrote: > Pester the maintainer? The maintainer is alumni. -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "fr

Re: cvsup broken on amd64?

Pester the maintainer? Adrian 2011/9/15 Alexander Zagrebin : >> I'm also using cvsup again, due to a problem I had with csup >> back in February >> 2011 >> > 813.html> . >> >> I didn't open a PR; I was under some time pressure and

RE: cvsup broken on amd64?

> I'm also using cvsup again, due to a problem I had with csup > back in February > 2011 > 813.html> . > > I didn't open a PR; I was under some time pressure and cvsup worked. There is a solution of the csup problem: http://www.f

Re: cvsup broken on amd64?

On Fri, 09 Sep 2011 13:47:37 +0200 Oliver Lehmann wrote: > > Kostik Belousov wrote: > > > For start, you should provide the information what exactly is the > > instruction that caused the fault. Show the disassembly from gdb > > for the function that caused the fault. > > Ok, I'm trying. I re

Re: cvsup broken on amd64?

On 09/08/11 14:52, b. f. wrote: I have an Atom 330 with 9.0-BETA2/amd64 installed. I did a pkg_add -r cvsup-without-gui at first after installation. Using cvsup, resulted in a core dump (illegal instruction). I then removed all ports, and installed cvsup-without-gui from source. Started cvsup..

Re: cvsup broken on amd64?

Kostik Belousov wrote: On Fri, Sep 09, 2011 at 06:20:57PM +0200, Oliver Lehmann wrote: (gdb) run Starting program: /usr/obj/amd64/usr/ports/net/cvsup-without-gui/work/cvsup-snap-16.1h/client/FBSD_AMD64/cvsup -g /usr/share/examples/cvsup/9-supfile Connected to cvsup.de.FreeBSD.org Updating

Re: cvsup broken on amd64?

On Fri, Sep 09, 2011 at 06:20:57PM +0200, Oliver Lehmann wrote: > > Kostik Belousov wrote: > > >On Fri, Sep 09, 2011 at 05:55:13PM +0300, Kostik Belousov wrote: > > >>Ok, please do the following: > >>run cvsup under the gdb. When SIGSEGV is raised, from the gdb prompt, do: > >>1. info registers

Re: cvsup broken on amd64?

Kostik Belousov wrote: On Fri, Sep 09, 2011 at 05:55:13PM +0300, Kostik Belousov wrote: Ok, please do the following: run cvsup under the gdb. When SIGSEGV is raised, from the gdb prompt, do: 1. info registers $rsp 2. info program This should print you the pid of the process, then do

Re: cvsup broken on amd64?

On Fri, Sep 09, 2011 at 05:55:13PM +0300, Kostik Belousov wrote: > On Fri, Sep 09, 2011 at 04:34:54PM +0200, Oliver Lehmann wrote: > > > > Kostik Belousov wrote: > > > > >On Fri, Sep 09, 2011 at 04:19:42PM +0200, Oliver Lehmann wrote: > > > > >>(gdb) bt > > >>#0 0x004d24c6 in tzload ()

Re: cvsup broken on amd64?

On Fri, Sep 09, 2011 at 04:34:54PM +0200, Oliver Lehmann wrote: > > Kostik Belousov wrote: > > >On Fri, Sep 09, 2011 at 04:19:42PM +0200, Oliver Lehmann wrote: > > >>(gdb) bt > >>#0 0x004d24c6 in tzload () > > > >Try to do "disas 0x4d24c6 0x4d24c6+30" from gdb prompt with the loaded >

Re: cvsup broken on amd64?

Kostik Belousov wrote: On Fri, Sep 09, 2011 at 04:19:42PM +0200, Oliver Lehmann wrote: (gdb) bt #0 0x004d24c6 in tzload () Try to do "disas 0x4d24c6 0x4d24c6+30" from gdb prompt with the loaded core. (gdb) disas 0x4d24c6 0x4d24c6+30 Dump of assembler code from 0x4d24c6 to 0x4d2

Re: cvsup broken on amd64?

On Fri, Sep 09, 2011 at 04:19:42PM +0200, Oliver Lehmann wrote: > > Kostik Belousov wrote: > > >I do not know, I was curious about 'illegal instruction' signal, > >which would indicate a problem in the compilation environment. > >Now you get segmentation violation, that is usually caused by a bu

Re: cvsup broken on amd64?

Kostik Belousov wrote: I do not know, I was curious about 'illegal instruction' signal, which would indicate a problem in the compilation environment. Now you get segmentation violation, that is usually caused by a bug in the program itself. running it outside gdb still results in an 'illega

Re: cvsup broken on amd64?

On 09/09/11 01:33, Oliver Lehmann wrote: Mike Tancsa wrote: Just curious as to why you need cvsup and not instead use csup that is in the base ? I got used to it in the past 12 years? But this is not realy the question. If it is "BROKEN" it should be marked as BROKEN or there should be a st

Re: cvsup broken on amd64?

On Fri, Sep 09, 2011 at 01:47:37PM +0200, Oliver Lehmann wrote: > > Kostik Belousov wrote: > > >For start, you should provide the information what exactly is the > >instruction that caused the fault. Show the disassembly from gdb > >for the function that caused the fault. > > Ok, I'm trying. I

Re: cvsup broken on amd64?

Kostik Belousov wrote: For start, you should provide the information what exactly is the instruction that caused the fault. Show the disassembly from gdb for the function that caused the fault. Ok, I'm trying. I recompiled cvsup for purpose with -DSTATIC How do I continue from the gdb outpu

Re: cvsup broken on amd64?

On Fri, Sep 09, 2011 at 11:30:46AM +0200, Oliver Lehmann wrote: > > Chris Rees wrote: > > >On 9 September 2011 06:33, Oliver Lehmann wrote: > >>I got used to it in the past 12 years? But this is not realy the question. > >>If it is "BROKEN" it should be marked as BROKEN or there should be a > >

Re: cvsup broken on amd64?

Chris Rees wrote: On 9 September 2011 06:33, Oliver Lehmann wrote: I got used to it in the past 12 years? But this is not realy the question. If it is "BROKEN" it should be marked as BROKEN or there should be a statement that it will not work with FreeBSD 9 on at least amd64 or we will have

Re: cvsup broken on amd64?

On 9 September 2011 06:33, Oliver Lehmann wrote: > > Mike Tancsa wrote: > >> Just curious as to why you need cvsup and not instead use csup that is >> in the base ? > > I got used to it in the past 12 years? But this is not realy the question. > If it is "BROKEN" it should be marked as BROKEN or

Re: cvsup broken on amd64?

Mike Tancsa wrote: Just curious as to why you need cvsup and not instead use csup that is in the base ? I got used to it in the past 12 years? But this is not realy the question. If it is "BROKEN" it should be marked as BROKEN or there should be a statement that it will not work with FreeBSD

Re: cvsup broken on amd64?

> I have an Atom 330 with 9.0-BETA2/amd64 installed. > > I did a pkg_add -r cvsup-without-gui at first after installation. > Using cvsup, resulted in a core dump (illegal instruction). > > I then removed all ports, and installed cvsup-without-gui from source. > Started cvsup... core dump again. > >