> BTW there is a known issue with the current 3.14
> branch version that crept in with the ca-over-tcp
> branch merge
FWIW:
I believe that at least some of the connect over TCP changes are also merged
into the cvs main trunk branch on launch pad, which I am working on. I have
a strong suspicion that I have resolved another (I don?t know if its related
to above mentioned issue or not) circuit shutdown related bug there today by
switching the order of these two fields in class tcpiiu. This exact issue
does not appear to be in the R3.14 trunk, but nevertheless I thought you
might benefit from my experience in case a similar issue is occurring there
in R3.14. The failure was related to the free list being destroyed before a
class that was using it was destroyed (which causes the memory where objects
live to be deallocated before they are destroyed).
comBufMemoryManager _comBufMemMgr;
comQueSend sendQue;
Jeff
______________________________________________________
Jeffrey O. Hill Email [email protected]
LANL MS H820 Voice 505 665 1831
Los Alamos NM 87545 USA FAX 505 665 5107
Message content: TSPA
> -----Original Message-----
> From: Andrew Johnson [mailto:[email protected]]
> Sent: Friday, August 13, 2010 4:09 PM
> To: Jeff Hill
> Cc: 'EPICS Core Talk'
> Subject: Re: some issues with "lp:epics-base" in bazaar
>
> On Friday 13 August 2010 16:26:27 Jeff Hill wrote:
> >
> > I found two significant bugs in base today, and if I fix them only on
> my
> > cvs main trunk ancestor branch there is a risk that they will be lost
> when
> > attempting to break that tree into independent merges. So I tried to
> > refresh my existing R3.14 development area. That didn?t work so I threw
> out
> > that one and tried to load a fresh one but there are still some issues.
> >
> > In any case when I try to download from the URL "lp:epics-base" using
> > bazaar explorer I see the error message below. I think this worked
> before,
> > but perhaps I am doing something stupid? In any case loading code from
> > "https://code.launchpad.net/epics-base" does work just fine.
> >
> > Invalid url supplied to transport:
> > "file:///home/phoebus3/ANJ/epics/base/export/base.bzr/trunk/": Win32
> file
> > urls start with file:///x:/, where x is a valid drive letter
>
> This is a known but benign problem with Bazaar explorer when you point it
> to a
> lightweight checkout. I reported it as a bug several months ago, see
> here:
> https://bugs.launchpad.net/bzr-explorer/+bug/550989
>
> If you want to get rid of the message don't do a lightweight checkout. I
> think a regular checkout should be fine, but I do know for sure that a
> normal
> branch is. However you can just ignore the message if you have disk
> space
> issues and prefer to stay lightweight.
>
> BTW there is a known issue with the current 3.14 branch version that
> crept in
> with the ca-over-tcp branch merge; it segfaults at shutdown of the client
> library when the tcpSendThread tries to use an already dead mutex. Ralph
> is
> looking at that right now, so don't go chasing it yourself without
> checking
> with him first.
>
> - Andrew
> --
> The best FOSS code is written to be read by other humans -- Harald Welte
- References:
- some issues with "lp:epics-base" in bazaar Jeff Hill
- Re: some issues with "lp:epics-base" in bazaar Andrew Johnson
- Navigate by Date:
- Prev:
Re: build error on R3.14 trunk Eric Norum
- Next:
Fixed: Segfaults in 3.14 branch since merging ca-over-tcp Ralph Lange
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: some issues with "lp:epics-base" in bazaar Andrew Johnson
- Next:
build error on R3.14 trunk Jeff Hill
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|