It is just sitting there doing nothing.
...tallations/sage/logs/pkgs» strace -p 3679
Process 3679 attached
^CProcess 3679 detached
...tallations/sage/logs/pkgs»
~» cat gdb.3679.log
(gdb) #0 0x00000000004011d8 in tuning_gf2x_mul1 (c=c@entry=0x658010,
a=1084672390, b=1756245403) at gen_mul1_w64k2.c:63
hi = <optimized out>
lo = <optimized out>
tmp = <optimized out>
A = {0, 1084672390, 2169344780, 3253426826}
#1 0x0000000000400ba1 in main (argc=<optimized out>, argv=<optimized
out>) at tuneup_1.c:127
i = <optimized out>
c0 = 0x658030
c = 0x658010
a = 0x7fa29ea52010
b = 0x7fa29e9d1010
st = 0
benchtime = <optimized out>
btime = 1000000
progname = 0x7fff89641610
"/home/punarbasu/Installations/sage/local/var/tmp/sage/build/gf2x-1.1/src/src/.libs/tune_gen_mul1_w64k2"
m = 313810596090
(gdb) A debugging session is active.
Inferior 1 [process 3679] will be detached.
Quit anyway? (y or n) [answered Y; input not from terminal]
Detaching from program:
/home/punarbasu/Installations/sage/local/var/tmp/sage/build/gf2x-1.1/src/src/.libs/tune_gen_mul1_w64k2,
process 3679
On 08/22/2013 04:55 PM, Francois Bissey wrote:
Can you attach with strace or gdb to see what the process is doing? If it does
anything at all that is.
Francois
On 22/08/2013, at 20:30, "P Purkayastha" <[email protected]> wrote:
Hi all,
Due to some change in my system sage no longer finishes compiling. This is
irrespective of whether it is sage-git or some released version. Usually it is
some tuning process that remains stuck for ever.
* At one point, it was atlas that was tuning for two whole days and never finished (irrespective of
whether I gave the ARCH as "base" or "Core2" or let it decide by itself). A
system installation of atlas finished compiling and installing in 20 min. Thanks to Burcin, I have
been able to use the system atlas and tricked sage into continuing with the rest of the
installation.
* Now, it is g2fx that is stuck for ever. It remains stuck at again a tuning
program that doesn't use any cpu and it will remain stuck like this for days on
end without any resolution. The log file of g2fx is attached and a screenshot
is attached which shows at which command it is stuck.
I am at a loss and I can't understand what exactly is impeding these tuning
processes. It is also a hindrance since I am unable to install any newer
version of sage on this particular machine, beyond what I had last compiled
(sage-5.11.beta3):
model name : Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz
If anyone can let me know how I can use a system installation of g2fx or just
let it use some generic tuning parameters, it will be great, and I can continue
with actually working with sage instead of fighting it!
Thanks,
basu.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
<gf2x-1.1.log>
<htop.jpg>
This email may be confidential and subject to legal privilege, it may
not reflect the views of the University of Canterbury, and it is not
guaranteed to be virus free. If you are not an intended recipient,
please notify the sender immediately and erase all copies of the message
and any attachments.
Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
information.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
