No, it seems to be a computation over a finite field (else you
shouldn't call npPower). So
0x2 is just 2 mod p.
Michael
On 31 Mai, 14:38, Martin Albrecht <[EMAIL PROTECTED]>
wrote:
> On Saturday 31 May 2008, mabshoff wrote:
>
>
>
> > Hello folks,
>
> > I am sure the subject line will make sure that next to no one reads
> > this message, but it is important for some of us.
>
> > Anyway, I finally got a pretty good lead what goes wrong when we
> > compute 1/y in a MV polynomial ring on Solaris using libSingular (1/x
> > also crashes, but that is not the point :).
>
> > I suspect the issue to be in coercion for the following reason:
>
> > Define a mv polynomial ring with say two indeterminates. Then
>
> > sage: 1/y
>
> > results in:
>
> > Program received signal SIGSEGV, Segmentation fault.
> > npPower (a=0x2, i=-74884, result=0x0) at modulop.cc:223
> > 223 void npPower (number a, int i, number * result)
> > Current language: auto; currently c++
> > (gdb) bt
> > #0 npPower (a=0x2, i=-74884, result=0x0) at modulop.cc:223
> > #1 0xfa178368 in npPower (a=0x2, i=-74884, result=0x0) at modulop.cc:
> > 236
> > #2 0xfa178368 in npPower (a=Cannot access memory at address
> > 0xff3ffde8
> > ) at modulop.cc:236
>
> I don't think 0x2 is a valid number in Singular. 0x5 would be since it uses
> two bits to make sure it doesn't confuse pointers with integers. So maybe
> this is just garbage memory it is pointing to?
>
> Martin
>
> --
> name: Martin Albrecht
> _pgp:http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
> _www:http://www.informatik.uni-bremen.de/~malb
> _jab: [EMAIL PROTECTED]
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
