On Sun, May 12, 2019 at 03:16:10PM +0300, Ilias Tsitsimpis wrote:
> On Mon, Mar 11, 2019 at 12:05PM, Adrian Bunk wrote:
> > On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote:
> > > See attached file with several debugging attempts.
> >
> > Looking at the code, the bug seems to be
On Mon, Mar 11, 2019 at 12:05PM, Adrian Bunk wrote:
> On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote:
> > See attached file with several debugging attempts.
>
> Looking at the code, the bug seems to be in
>
On Sat, Apr 27, 2019 at 09:35:51AM -0700, Sean Whitton wrote:
> Hello,
>
> On Sat 27 Apr 2019 at 11:14AM -04, Antoine Beaupré wrote:
>
> > ... and it looks like it's a bug / limitation in ghc itself...
>
> Right, it has been reassigned to ghc.
>
> > From the Toronto BSP's point of view, this
On 2019-04-27 09:35:51, Sean Whitton wrote:
> Hello,
>
> On Sat 27 Apr 2019 at 11:14AM -04, Antoine Beaupré wrote:
>
>> ... and it looks like it's a bug / limitation in ghc itself...
>
> Right, it has been reassigned to ghc.
>
>> From the Toronto BSP's point of view, this is looking more and more
Hello,
On Sat 27 Apr 2019 at 11:14AM -04, Antoine Beaupré wrote:
> ... and it looks like it's a bug / limitation in ghc itself...
Right, it has been reassigned to ghc.
> From the Toronto BSP's point of view, this is looking more and more like
> a "well, this means we won't support that
On Sat, Apr 27, 2019 at 12:12:10PM -0400, Antoine Beaupré wrote:
> On 2019-04-27 18:30:32, Adrian Bunk wrote:
> > On Sat, Apr 27, 2019 at 11:14:33AM -0400, Antoine Beaupré wrote:
> >> user debian-rele...@lists.debian.org
> >> usertags 915333 + bsp-2019-04-ca-toronto
> >> thank you
> >>
> >> On
On 2019-04-27 18:30:32, Adrian Bunk wrote:
> On Sat, Apr 27, 2019 at 11:14:33AM -0400, Antoine Beaupré wrote:
>> user debian-rele...@lists.debian.org
>> usertags 915333 + bsp-2019-04-ca-toronto
>> thank you
>>
>> On 2019-04-09 08:46:10, Adrian Bunk wrote:
>> > On Sun, Apr 07, 2019 at 02:01:33PM
On Sat, Apr 27, 2019 at 11:14:33AM -0400, Antoine Beaupré wrote:
> user debian-rele...@lists.debian.org
> usertags 915333 + bsp-2019-04-ca-toronto
> thank you
>
> On 2019-04-09 08:46:10, Adrian Bunk wrote:
> > On Sun, Apr 07, 2019 at 02:01:33PM +0200, Darshaka Pathirana wrote:
> >> Hey,
> >>
>
user debian-rele...@lists.debian.org
usertags 915333 + bsp-2019-04-ca-toronto
thank you
On 2019-04-09 08:46:10, Adrian Bunk wrote:
> On Sun, Apr 07, 2019 at 02:01:33PM +0200, Darshaka Pathirana wrote:
>> Hey,
>>
>> On Mon, 11 Mar 2019 12:05:55 +0200 Adrian Bunk wrote:
>> > On Thu, Jan 31, 2019
On Sun, Apr 07, 2019 at 02:01:33PM +0200, Darshaka Pathirana wrote:
> Hey,
>
> On Mon, 11 Mar 2019 12:05:55 +0200 Adrian Bunk wrote:
> > On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote:
> > > Hello Everyone,
> > > I own a qnap ts-119pII with a similar cpu.
> > >
> > > See
Hey,
On Mon, 11 Mar 2019 12:05:55 +0200 Adrian Bunk wrote:
> On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote:
> > Hello Everyone,
> > I own a qnap ts-119pII with a similar cpu.
> >
> > See attached file with several debugging attempts.
I took some time and wanted to reproduce
Control: severity -1 serious
Control: reassign -1 ghc 8.4.4+dfsg1-1
Control: affects -1 git-annex
On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote:
> Hello Everyone,
> I own a qnap ts-119pII with a similar cpu.
>
> See attached file with several debugging attempts.
Thanks a
Package: git-annex
Version: 7.20190129-2
Followup-For: Bug #915333
Dear Maintainer,
FYI this still exists in 7.20190129-2
Thanks,
Julian Calaby
Hello Everyone,
I own a qnap ts-119pII with a similar cpu.
See attached file with several debugging attempts.
With my limited assembly knowledge I got to this instruction,
where the backtrace command still shows all of the stack:
(gdb) bt
#0 0x03718a2c in stg_returnToStackTop$def ()
Package: git-annex
Version: 7.20190122-1
Followup-For: Bug #915333
Dear Maintainer,
This also happens on Marvel Kirkwood systems, e.g. a GoFlex NAS.
I suspect that this is a code generation problem further upstream and not
necessarily a git-annex specific problem and probably happens on all
Package: git-annex
Version: 7.20181121-1
Severity: important
Dear Maintainer,
I wanted to use git-annex on this machine (Fujitsu Q700 NAS), but it Crashes
with
"Illegal Instruction". I don't have these problems with other Packages or with
the
upstream build of git-annex.
Many Thanks for
16 matches
Mail list logo
