On Nov 30, 2010, at 1:04 PM, Piotr Esden-Tempski wrote: > On Nov 30, 2010, at 12:03 PM, Steve Bennett wrote: > >> On 01/12/2010, at 12:12 AM, Edgar Grimberg wrote: >> >>> On Tue, Nov 30, 2010 at 1:02 PM, Øyvind Harboe <[email protected]> >>> wrote: >>>> 32 vs. 64 bit problem? >>> >>> Wouldn't that be interesting? :) >>> Are there Linux 64 users out there that can try it out? >> >> I note that Domen Puncer is having a similar problem. >> Also looks like 64 bit from the stack trace. >> >> Piotr, can you try building 32 bit? >> Something like: >> >> ./configure ... CFLAGS="-arch i386 -O0 -g" > > > Yes sir! I just tested the newest version in git of oocd with -m32 on Mac OS > X Snow leopard and it does NOT crash. So it is definitely a 64 bit problem > here. > > Thanks for pointing that out! > > I will try to find a 64bit linux machine and see if I get the same error > there. (maybe also someone else can take a stab at it?)
Ok I just tested on 64bit ubuntu linux machine. And "sadly" it works there. :( So the only way to trigger the segfault currently is running 64 bit openocd binary on Snow Leopard. :( Cheers Esden -- Blog: http://www.esden.net Projects: http://open-bldc.org http://paparazziuav.org http://github.org/esden/floss-jtag http://github.org/esden/summon-arm-toolchain
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
