Re: Segfault with mismatching -j values on AMD64

On Thu, 2009-03-12 at 21:03 +0000, Geoffrey Clements wrote:
> On Thursday 12 Mar 2009, Francesco Romani wrote:
> > On Thu, 2009-03-12 at 15:33 +0000, Geoffrey Clements wrote:
> > > I recently upgraded my PC from an x86 to an x86_64 X 4 architecture and
> > > well used transcode recipes started segfaulting.
> > >
> > > After a bit of investigation I found that it is the "-j t,l,b,r" switch
> > > that's causing the problem; the segfault occurs if t <> b or l <> r.
> >
> > Hi,
> >
> > thanks for the report. Please file a bug here:
> > http://developer.berlios.de/bugs/?group_id=10094
> > for tracking purposes.
> 
> I'm attempting to get more information with gdb first so that I can file a 
> complete bug report, however using code from:
> svn://svn.berlios.de/tcforge/transcode/trunk
> which I think is version 1.1.1

No, the development happens on mercurial (HG). The SVN holds only former
experiments (waiting for a revamp) :)

Bests,

-- 
Francesco Romani // Ikitt
http://fromani.exit1.org  ::: transcode homepage
http://tcforge.berlios.de ::: transcode experimental forge