Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)

2012-07-02 Thread Steve McIntyre
On Mon, Jul 02, 2012 at 03:29:55PM +0100, Steve McIntyre wrote: >On Sun, Jul 01, 2012 at 09:15:45PM +, Thorsten Glaser wrote: >>maximilian attems dixit: >> >>>so could it be out of blindness that we didn't properly build with >>>thumb instruction in Debian? >> >>I’ve tried enabling thumb, but

Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)

2012-07-02 Thread Steve McIntyre
On Sun, Jul 01, 2012 at 09:15:45PM +, Thorsten Glaser wrote: >maximilian attems dixit: > >>so could it be out of blindness that we didn't properly build with >>thumb instruction in Debian? > >I’ve tried enabling thumb, but the bugs didn’t go away with >that either. There's a reason for tha

Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)

2012-07-01 Thread Steve McIntyre
On Sun, Jul 01, 2012 at 08:57:30PM +, maximilian attems wrote: >On Fri, Jun 29, 2012 at 06:13:34PM +0100, Steve McIntyre wrote: >> On Thu, Jun 28, 2012 at 06:59:34PM +0200, maximilian attems wrote: >> >On Tue, 19 Jun 2012, Steve McIntyre wrote: >> >> * There's a real bug in the ARM assembly ve

Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)

2012-07-01 Thread Thorsten Glaser
maximilian attems dixit: >so could it be out of blindness that we didn't properly build with >thumb instruction in Debian? I’ve tried enabling thumb, but the bugs didn’t go away with that either. bye, //mirabilos -- 13:37⎜«Natureshadow» Deep inside, I hate mirabilos. I mean, he's a good guy. Bu

Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)

2012-07-01 Thread maximilian attems
On Fri, Jun 29, 2012 at 06:13:34PM +0100, Steve McIntyre wrote: > On Thu, Jun 28, 2012 at 06:59:34PM +0200, maximilian attems wrote: > >On Tue, 19 Jun 2012, Steve McIntyre wrote: > >> * There's a real bug in the ARM assembly version of longjmp in > >>usr/klibc/arch/arm/setjmp.S: it will always

Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)

2012-06-29 Thread Steve McIntyre
On Thu, Jun 28, 2012 at 06:59:34PM +0200, maximilian attems wrote: >On Tue, 19 Jun 2012, Steve McIntyre wrote: > >> >> More debugging results: >> >> * If I replace -Os with -O0 to disable optimisation, the crash goes >>away too. Suggests (maybe) a compiler bug here... > >nasty. :| > >> * T

Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)

2012-06-28 Thread maximilian attems
On Tue, 19 Jun 2012, Steve McIntyre wrote: > > More debugging results: > > * If I replace -Os with -O0 to disable optimisation, the crash goes >away too. Suggests (maybe) a compiler bug here... nasty. :| > * There's a real bug in the ARM assembly version of longjmp in >usr/klibc/arc

Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)

2012-06-18 Thread Steve McIntyre
On Sun, Jun 17, 2012 at 09:58:46PM +, Thorsten Glaser wrote: >Steve McIntyre dixit: > >>Digging further with the built-in debug TRACE function, I can see >>problems in usr/dash/eval.c:evalcommand(). The place where cmd >>switches from non-NULL to NULL is >> >> status = redirectsafe(cmd->ncmd.r

Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)

2012-06-17 Thread Thorsten Glaser
Steve McIntyre dixit: >Digging further with the built-in debug TRACE function, I can see >problems in usr/dash/eval.c:evalcommand(). The place where cmd >switches from non-NULL to NULL is > > status = redirectsafe(cmd->ncmd.redirect, REDIR_PUSH|REDIR_SAVEFD2); Yeah, I got approximately so far to

Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)

2012-06-17 Thread Steve McIntyre
On Thu, May 31, 2012 at 07:18:51PM +, Thorsten Glaser wrote: >shawn dixit: > >>"I am at wit's end." would be how I would translate it. > >Ah, thanks ;-) > >>no idea how to fix segfaults, sorry :). > >No problem. I think I’ve done my share too, though… > >>However I don't think the linked is

Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)

2012-05-31 Thread Thorsten Glaser
shawn dixit: >"I am at wit's end." would be how I would translate it. Ah, thanks ;-) >no idea how to fix segfaults, sorry :). No problem. I think I’ve done my share too, though… >However I don't think the linked issue is the right one, as it has been >described as not being regular, and has be

Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)

2012-05-31 Thread shawn
>On the other hand, my Latin is at its end (does this saying translate >into English?), I’ve got no idea how to track this down. "I am at wit's end." would be how I would translate it. http://www.thefreedictionary.com/at+%28one%27s%29+wits%27+end Idioms: at (one's) wits' end At the limit of on

Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)

2012-05-27 Thread Thorsten Glaser
maximilian attems dixit: >ok I see, thus #634890 has rc severity. No, last time I’ve thought armhf were RC just because they ended up being in the main archive I was told off; armhf and s390x still are not RC. But “we” should process it as if it were RC, probably. On the other hand, my Latin is

Bug#634890: [klibc] klibc issues on armhf (not Debian/armel)

2012-05-27 Thread maximilian attems
On Sun, May 27, 2012 at 02:34:00PM +, Thorsten Glaser wrote: > maximilian attems dixit: > > >I don't know if klibc-utils provided binaries do work on armhf? > > In this case, sh and sh.shared don’t work on armhf, either with > or without thumb. The Debian package builds without thumb. ok I s