Goulet
Sent: Wednesday, September 10, 2014 4:58 PM
Subject: Re: Bug#684580: SIGSEGV in torsocks 2.0.0-1
Hi,
intrigeri wrote (30 Aug 2014 20:18:33 GMT) :
> JS, may you please file a separate bug?
I have done it myself, eventually: #761120. Please keep further
discussion on that new bug, inst
Hi,
intrigeri wrote (30 Aug 2014 20:18:33 GMT) :
> JS, may you please file a separate bug?
I have done it myself, eventually: #761120. Please keep further
discussion on that new bug, instead of the old #684580 one, that was
fixed in torsocks 2.0. Thanks!
Cheers,
--
intrigeri
--
To UNSUBSCRIBE
On 03 Sep (08:17:26), JS wrote:
> I've attached text files with the bt full for midori and chromium.
>
Hrm, unfortunately I can't get the exact call site since you are using I
suppose the package which does not provide debug symbol.
However, I think I understand what's going on here. In a nutshe
l Message -
> From: David Goulet
> To: intrigeri
> Cc: JS ; 684...@bugs.debian.org
> Sent: Wednesday, September 3, 2014 9:10 AM
> Subject: Re: Bug#684580: SIGSEGV in torsocks 2.0.0-1
>
> On 30 Aug (13:18:33), intrigeri wrote:
> > Hi,
> >
> > JS wrote (30
sions of packages torsocks depends on:
ii libc6 2.19-1
while the newest version is libc6 2.19-9 in jessie?
thanks,
--jack
- Original Message -
From: David Goulet
To: intrigeri
Cc: JS ; 684...@bugs.debian.org
Sent: Wednesday, September 3, 2014 9:10 AM
Subject: Re: Bug#684580: SIGSE
gt; To: intrigeri
> Cc: JS ; 684...@bugs.debian.org
> Sent: Wednesday, September 3, 2014 9:10 AM
> Subject: Re: Bug#684580: SIGSEGV in torsocks 2.0.0-1
>
> On 30 Aug (13:18:33), intrigeri wrote:
> > Hi,
> >
> > JS wrote (30 Aug 2014 14:59:03 GMT) :
> > >
On 30 Aug (13:18:33), intrigeri wrote:
> Hi,
>
> JS wrote (30 Aug 2014 14:59:03 GMT) :
> > I've just upgrade torsocks from 1.3-3 to 2.0.0-1 and have found that
> > it gets SIGSEGV now
>
> > Below is the backtrace from gdb after running:
> > . torsocks on
> > midori#
Hi,
JS wrote (30 Aug 2014 14:59:03 GMT) :
> I've just upgrade torsocks from 1.3-3 to 2.0.0-1 and have found that
> it gets SIGSEGV now
> Below is the backtrace from gdb after running:
> . torsocks on
> midori# but happens with most other apps as well
I've seen a seg
I've just upgrade torsocks from 1.3-3 to 2.0.0-1 and have found that it gets
SIGSEGV now
when before it worked fine.
Below is the backtrace from gdb after running:
. torsocks on
midori# but happens with most other apps as well
I have used the exact config file
9 matches
Mail list logo