[sage-support] Re: problem with sage-vmware 3.4.1 on windows xp

2009-05-08 Thread Alessandro Torre

Any news?
Do you think you will need me for future testing or can I delete the
bugged vmware image?
And how are things going?
Have you solved the problem?

Cheers
A.

On 5 Mag, 12:13, Alessandro Torre 
wrote:
> Hi.
>
> disassemble.txt does contain the output from "disassemble $pc
> +32,$pc-32"
>
> Instead "disassemble $pc+32 $pc-32" produces no output:
>
> Dump of assembler code from 0xb76ce853 to 0xb76ce813:
> End of assembler dump.
>
> And the output of "disassemble $pc-32 $pc+32":
>
> Dump of assembler code from 0xb76ce813 to 0xb76ce853:
> 0xb76ce813 <__gmpz_set_str+451>:  rorl   $0x31,-0x378ad42a(%ecx)
> 0xb76ce81a <__gmpz_set_str+458>:  rclb   %cl,0x56(%edx)
> 0xb76ce81d <__gmpz_set_str+461>:  fildll (%esp)
> 0xb76ce820 <__gmpz_set_str+464>:  add    $0x8,%esp
> 0xb76ce823 <__gmpz_set_str+467>:  mov    0x10(%ebp),%edi
> 0xb76ce826 <__gmpz_set_str+470>:  lea    (%edi,%edi,4),%edx
> 0xb76ce829 <__gmpz_set_str+473>:  mov    -0x2c(%ebx),%eax
> 0xb76ce82f <__gmpz_set_str+479>:  fdivl  0x4(%eax,%edx,4)
> 0xb76ce833 <__gmpz_set_str+483>:  fisttpl -0x20(%ebp)
> 0xb76ce836 <__gmpz_set_str+486>:  mov    -0x20(%ebp),%eax
> 0xb76ce839 <__gmpz_set_str+489>:  lea    0x1f(%eax),%edx
> 0xb76ce83c <__gmpz_set_str+492>:  cmp    $0x,%eax
> 0xb76ce83f <__gmpz_set_str+495>:  cmovle %edx,%eax
> 0xb76ce842 <__gmpz_set_str+498>:  sar    $0x5,%eax
> 0xb76ce845 <__gmpz_set_str+501>:  add    $0x2,%eax
> 0xb76ce848 <__gmpz_set_str+504>:  mov    -0x3c(%ebp),%edx
> 0xb76ce84b <__gmpz_set_str+507>:  cmp    (%edx),%eax
> 0xb76ce84d <__gmpz_set_str+509>:  jg     0xb76ce917 <__gmpz_set_str
> +711>
> End of assembler dump.
>
> I hope that's all.
>
> Cheers
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-support] Re: problem with sage-vmware 3.4.1 on windows xp

2009-05-05 Thread Alessandro Torre

Hi.

disassemble.txt does contain the output from "disassemble $pc
+32,$pc-32"

Instead "disassemble $pc+32 $pc-32" produces no output:

Dump of assembler code from 0xb76ce853 to 0xb76ce813:
End of assembler dump.

And the output of "disassemble $pc-32 $pc+32":

Dump of assembler code from 0xb76ce813 to 0xb76ce853:
0xb76ce813 <__gmpz_set_str+451>:rorl   $0x31,-0x378ad42a(%ecx)
0xb76ce81a <__gmpz_set_str+458>:rclb   %cl,0x56(%edx)
0xb76ce81d <__gmpz_set_str+461>:fildll (%esp)
0xb76ce820 <__gmpz_set_str+464>:add$0x8,%esp
0xb76ce823 <__gmpz_set_str+467>:mov0x10(%ebp),%edi
0xb76ce826 <__gmpz_set_str+470>:lea(%edi,%edi,4),%edx
0xb76ce829 <__gmpz_set_str+473>:mov-0x2c(%ebx),%eax
0xb76ce82f <__gmpz_set_str+479>:fdivl  0x4(%eax,%edx,4)
0xb76ce833 <__gmpz_set_str+483>:fisttpl -0x20(%ebp)
0xb76ce836 <__gmpz_set_str+486>:mov-0x20(%ebp),%eax
0xb76ce839 <__gmpz_set_str+489>:lea0x1f(%eax),%edx
0xb76ce83c <__gmpz_set_str+492>:cmp$0x,%eax
0xb76ce83f <__gmpz_set_str+495>:cmovle %edx,%eax
0xb76ce842 <__gmpz_set_str+498>:sar$0x5,%eax
0xb76ce845 <__gmpz_set_str+501>:add$0x2,%eax
0xb76ce848 <__gmpz_set_str+504>:mov-0x3c(%ebp),%edx
0xb76ce84b <__gmpz_set_str+507>:cmp(%edx),%eax
0xb76ce84d <__gmpz_set_str+509>:jg 0xb76ce917 <__gmpz_set_str
+711>
End of assembler dump.

I hope that's all.

Cheers
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-support] problem with sage-vmware 3.4.1 on windows xp

2009-05-04 Thread Alessandro Torre
I forgot the files...

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---

Dump of assembler code for function __gmpz_set_str:
0xb76f8650 <__gmpz_set_str+0>:  push   %ebp
0xb76f8651 <__gmpz_set_str+1>:  mov%esp,%ebp
0xb76f8653 <__gmpz_set_str+3>:  push   %edi
0xb76f8654 <__gmpz_set_str+4>:  push   %esi
0xb76f8655 <__gmpz_set_str+5>:  push   %ebx
0xb76f8656 <__gmpz_set_str+6>:  sub$0x5c,%esp
0xb76f8659 <__gmpz_set_str+9>:  call   0xb76e2107 <__i686.get_pc_thunk.bx>
0xb76f865e <__gmpz_set_str+14>: add$0x2ec86,%ebx
0xb76f8664 <__gmpz_set_str+20>: mov0x8(%ebp),%eax
0xb76f8667 <__gmpz_set_str+23>: mov%eax,-0x3c(%ebp)
0xb76f866a <__gmpz_set_str+26>: mov0xc(%ebp),%esi
0xb76f866d <__gmpz_set_str+29>: mov%gs:0x14,%edx
0xb76f8674 <__gmpz_set_str+36>: mov%edx,-0x10(%ebp)
0xb76f8677 <__gmpz_set_str+39>: xor%edx,%edx
0xb76f8679 <__gmpz_set_str+41>: cmpl   $0x24,0x10(%ebp)
0xb76f867d <__gmpz_set_str+45>: jg 0xb76f8737 <__gmpz_set_str+231>
0xb76f8683 <__gmpz_set_str+51>: mov-0x3c(%ebx),%ecx
0xb76f8689 <__gmpz_set_str+57>: mov%ecx,-0x2c(%ebp)
0xb76f868c <__gmpz_set_str+60>: call   0xb76e1f54 <__ctype_b_...@plt>
0xb76f8691 <__gmpz_set_str+65>: mov%eax,-0x28(%ebp)
0xb76f8694 <__gmpz_set_str+68>: mov(%eax),%ecx
0xb76f8696 <__gmpz_set_str+70>: movzbl (%esi),%eax
0xb76f8699 <__gmpz_set_str+73>: movzbl %al,%edx
0xb76f869c <__gmpz_set_str+76>: mov%edx,-0x44(%ebp)
0xb76f869f <__gmpz_set_str+79>: add$0x1,%esi
0xb76f86a2 <__gmpz_set_str+82>: testb  $0x20,0x1(%ecx,%edx,2)
0xb76f86a7 <__gmpz_set_str+87>: jne0xb76f8696 <__gmpz_set_str+70>
0xb76f86a9 <__gmpz_set_str+89>: cmp$0x2d,%al
0xb76f86ab <__gmpz_set_str+91>: je 0xb76f8767 <__gmpz_set_str+279>
0xb76f86b1 <__gmpz_set_str+97>: movl   $0x0,-0x30(%ebp)
0xb76f86b8 <__gmpz_set_str+104>:mov$0xa,%eax
0xb76f86bd <__gmpz_set_str+109>:mov0x10(%ebp),%edx
0xb76f86c0 <__gmpz_set_str+112>:test   %edx,%edx
0xb76f86c2 <__gmpz_set_str+114>:cmovne 0x10(%ebp),%eax
0xb76f86c6 <__gmpz_set_str+118>:mov-0x44(%ebp),%edx
0xb76f86c9 <__gmpz_set_str+121>:mov-0x2c(%ebp),%edi
0xb76f86cc <__gmpz_set_str+124>:movzbl (%edx,%edi,1),%edx
0xb76f86d0 <__gmpz_set_str+128>:cmp%edx,%eax
0xb76f86d2 <__gmpz_set_str+130>:jle0xb76f8760 <__gmpz_set_str+272>
0xb76f86d8 <__gmpz_set_str+136>:mov0x10(%ebp),%edi
0xb76f86db <__gmpz_set_str+139>:test   %edi,%edi
0xb76f86dd <__gmpz_set_str+141>:jne0xb76f86ff <__gmpz_set_str+175>
0xb76f86df <__gmpz_set_str+143>:cmpl   $0x30,-0x44(%ebp)
0xb76f86e3 <__gmpz_set_str+147>:je 0xb76f889c <__gmpz_set_str+588>
0xb76f86e9 <__gmpz_set_str+153>:movl   $0xa,0x10(%ebp)
0xb76f86f0 <__gmpz_set_str+160>:cmpl   $0x30,-0x44(%ebp)
0xb76f86f4 <__gmpz_set_str+164>:jne0xb76f8705 <__gmpz_set_str+181>
0xb76f86f6 <__gmpz_set_str+166>:movzbl (%esi),%edx
0xb76f86f9 <__gmpz_set_str+169>:mov%edx,-0x44(%ebp)
0xb76f86fc <__gmpz_set_str+172>:add$0x1,%esi
0xb76f86ff <__gmpz_set_str+175>:cmpl   $0x30,-0x44(%ebp)
0xb76f8703 <__gmpz_set_str+179>:je 0xb76f86f6 <__gmpz_set_str+166>
0xb76f8705 <__gmpz_set_str+181>:mov-0x44(%ebp),%edi
0xb76f8708 <__gmpz_set_str+184>:testb  $0x20,0x1(%ecx,%edi,2)
0xb76f870d <__gmpz_set_str+189>:jne0xb76f86f6 <__gmpz_set_str+166>
0xb76f870f <__gmpz_set_str+191>:test   %edi,%edi
0xb76f8711 <__gmpz_set_str+193>:jne0xb76f877c <__gmpz_set_str+300>
0xb76f8713 <__gmpz_set_str+195>:mov-0x3c(%ebp),%eax
0xb76f8716 <__gmpz_set_str+198>:movl   $0x0,0x4(%eax)
0xb76f871d <__gmpz_set_str+205>:xor%eax,%eax
0xb76f871f <__gmpz_set_str+207>:mov-0x10(%ebp),%edi
0xb76f8722 <__gmpz_set_str+210>:xor%gs:0x14,%edi
0xb76f8729 <__gmpz_set_str+217>:jne0xb76f88ee <__gmpz_set_str+670>
0xb76f872f <__gmpz_set_str+223>:lea-0xc(%ebp),%esp
0xb76f8732 <__gmpz_set_str+226>:pop%ebx
0xb76f8733 <__gmpz_set_str+227>:pop%esi
0xb76f8734 <__gmpz_set_str+228>:pop%edi
0xb76f8735 <__gmpz_set_str+229>:pop%ebp
0xb76f8736 <__gmpz_set_str+230>:ret
0xb76f8737 <__gmpz_set_str+231>:cmpl   $0x3e,0x10(%ebp)
0xb76f873b <__gmpz_set_str+235>:jg 0xb76f8760 <__gmpz_set_str+272>
0xb76f873d <__gmpz_set_str+237>:mov-0x3c(%ebx),%edi
0xb76f8743 <__gmpz_set_str+243>:add$0xe0,%edi
0xb76f8749 <__gmpz_set_str+249>:mov%edi,-0x2c(%ebp)
0xb76f874c <__gmpz_set_str+252>:jmp0xb76f868c <__gmpz

[sage-support] problem with sage-vmware 3.4.1 on windows xp

2009-05-04 Thread Alessandro Torre
Hi.Here is the requested output
(
http://groups.google.com/group/sage-support/browse_thread/thread/df502c9e16565886
)

Good Work.
Alessandro

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-support] Re: problem with sage-vmware 3.4.1 on windows xp

2009-05-04 Thread Alessandro Torre

putty cannot connect to the address you say.
I think it is normal if sage fails to start.

I tried to use standard gdb logging to file, but I can't find gdb.txt
I tried to set another file, but it seems it doesn't work (I used "set
logging file mylog.txt")
Any hints?
I could ftp the log file to a server of mine and then download it from
within winxp.


On 3 Mag, 20:20, William Stein  wrote:
>
>
> VMware doesn't by default make this easy at all.  One thing you can do
> is use a standard windows ssh program (e.g., putty is a good free
> one), and ssh to the vmware machine.
> Use the login "login" and password "sage".  The address that you ssh
> to is the same one
> that you use to connect to the sage notebook.    Copy and paste, etc.,
> should work very well with putty.
>
> --
> William Stein
> Associate Professor of Mathematics
> University of Washingtonhttp://wstein.org
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-support] Re: problem with sage-vmware 3.4.1 on windows xp

2009-05-03 Thread Alessandro Torre

@William
I've build sage as you said and it works. Great!

@Michael
I've installed gdb and followed your instruction, but I dunno how to
copy the output.
(I'm sorry for such a trivial question, but this is my first
experience with a unix shell)
And which address should I mail to what you need?

Thanks to both of you!
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-support] Re: problem with sage-vmware 3.4.1 on windows xp

2009-05-03 Thread Alessandro Torre

On 2 Mag, 23:29, mabshoff 
wrote:
> On May 2, 2:04 pm, William Stein  wrote:
>
> > On Sat, May 2, 2009 at 8:53 AM, Alessandro Torre
>
> 
>
> > > Is it possible that my processor is obsolete for this version of Sage?
>
> > Yes.
>
> > What is the output of
>
> >    cat /proc/cpuinfo
>
> I doubt this will be helpful. Having thought about this for a while my
> guess is that some of the instructions used in MPIR might cause this.
> When I wrote a script to detect "advanced" instructions I only
> concentrated on SSE instructions since back then it was the major (and
> only known) problem. If gdb is installed in the VMWare image we can
> start Sage under gdb, get a back trace (to figure out which library it
> is) and then disassemble around the current pc so that I can fix
> this :)
>
> So far no one has provided information to what is wrong, i.e. which
> instruction[s] in what library causes this, so I cannot even start to
> fix this.
>
> Cheers,
>
> Michael

"So far no one has provided information to what is wrong, i.e. which
instruction[s] in what library causes this, so I cannot even start to
fix this."

Can I help somehow?
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-support] Re: [help!] problem with sage-vmware 3.4.1 on windows xp

2009-05-03 Thread Alessandro Torre



On 2 Mag, 23:04, William Stein  wrote:
> On Sat, May 2, 2009 at 8:53 AM, Alessandro Torre
>
>
>
>  wrote:
>
> > Hello to everybody.
> > I can't make Sage works on windows and I'm going crazy.
>
> > When typing "sage" or "notebook" on the welcome screen of the VMware
> > Player nothing happens.
> > If I type "manage" and then "sage" the following message appears:
>
> > --
> > | Sage Version 3.4.1, (etc..) |
> > --
> > usr/local/sage/local/bin/sage-sage: line 198:  3558 Illegal
> > instruction     sage-ipython "$@" -i
>
> > What have I missed?
>
> > VMware 2.5.2 on Windows XP sp3 .
> > AMD Athlon 64 Processor 3000+ 2.00 GHz, 1.50 GB Ram
> > 0 MB Paging File
>
> > Is it possible that my processor is obsolete for this version of Sage?
>
> Yes.
>
> What is the output of
>
>    cat /proc/cpuinfo
>
> after you login as "manage"?
>
> Anyway, you might have to build Sage from source.  This is actually
> easier than you might think.  Do all of the following after login as
> "manage" and typing  "sudo su".
>
> 1. Delete /usr/local/sage, then
>    cd /usr/local; rm -rf sage
> 2. download sage-3.4.1.tar by typing
>     wgethttp://sagemath.org/src/sage-3.4.1.tar
> 3. extract it,
>      tar xf sage-3.4.1.tar
> 4. move it to be /usr/local/sage, and
>      mv sage-3.4.1 sage
> 5. build Sage -- this will take a few hours (no manual intervention):
>       cd sage; make
>
> > I've set my paging file to 0 MB. Could it be a problem?
>
> You could try setting it larger and see what happens.
>
>  -- William

Thanks a lot for this step to step procedure.
I found your reply on a similar post too, but I didn't figure out I
could make it in winxp thanks to vmware.

The output you asked for:

processor  : 0
vendor_id   : AuthenticAMD
cpu family  : 15
model: 12
model name   : AMD Athlon(tm) 64 Processor 3000+
stepping : 0
cpu MHz: 1999.515
cache size : 512 KB
fdiv_bug : no
hlt_bug  : no
f00f_bug: no
coma_bug : no
fpu: yes
fpu_exception: yes
cpuid level : 1
wp: yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr
pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext
3dnowext 3dnow up ts fid vid ttp
bogomips  : 4016.23


P.S: Setting a proper paging file didn't help.

Alessandro
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---



[sage-support] [help!] problem with sage-vmware 3.4.1 on windows xp

2009-05-02 Thread Alessandro Torre

Hello to everybody.
I can't make Sage works on windows and I'm going crazy.

When typing "sage" or "notebook" on the welcome screen of the VMware
Player nothing happens.
If I type "manage" and then "sage" the following message appears:

--
| Sage Version 3.4.1, (etc..) |
--
usr/local/sage/local/bin/sage-sage: line 198:  3558 Illegal
instruction sage-ipython "$@" -i


What have I missed?

VMware 2.5.2 on Windows XP sp3 .
AMD Athlon 64 Processor 3000+ 2.00 GHz, 1.50 GB Ram
0 MB Paging File

Is it possible that my processor is obsolete for this version of Sage?
I've set my paging file to 0 MB. Could it be a problem?

Thanks in advance.
Alessandro

--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---