Back to Forum | View unanswered posts | View active topics
| Topic review - Singular 3.0.1-1 segment fault/Bus error with Cygwin |
| Author |
Message |
|
|
| |
Post subject: |
|
 |
|
wienand wrote: There is an error in the Shortcut "Singular (Emacs and X-Server)". {Fix as in my previous posting.}
Yes, that shortuct change works. [quote="wienand"]There is an error in the Shortcut "Singular (Emacs and X-Server)". {Fix as in my previous posting.}
[/quote]
Yes, that shortuct change works.
|
|
|
 |
Posted: Wed Aug 02, 2006 9:39 pm |
|
|
 |
|
|
| |
Post subject: |
|
|
|
There is an error in the Shortcut "Singular (Emacs and X-Server)". You can correct it, when you rightclick on it and choose options. Now change the entry in Target from Code: C:ProgrammeCygWinusrX11R6binrun.exe bash -l -c "/usr/share/lib/Singular/startxserver.bat && sleep 1 && ESingular" to Code: C:ProgrammeCygWinusrX11R6binrun.exe bash -l -c "/usr/lib/Singular/startxserver.bat && sleep 1 && ESingular" It will be fixed in the upcomming 3-0-2 release. I still have no solution for the path problem. There is an error in the Shortcut "Singular (Emacs and X-Server)". You can correct it, when you rightclick on it and choose options. Now change the entry in Target from
[code]C:ProgrammeCygWinusrX11R6binrun.exe bash -l -c "/usr/share/lib/Singular/startxserver.bat && sleep 1 && ESingular"[/code]
to
[code]C:ProgrammeCygWinusrX11R6binrun.exe bash -l -c "/usr/lib/Singular/startxserver.bat && sleep 1 && ESingular"[/code]
It will be fixed in the upcomming 3-0-2 release. I still have no solution for the path problem.
|
|
|
|
Posted: Wed Aug 02, 2006 6:34 pm |
|
|
|
|
|
| |
Post subject: |
|
|
|
murray wrote: I can confirm that those fixes do work.... Also now: (5) Shortcut "Singular (rxvt)" also runs Singular OK. [quote="murray"]
I can confirm that those fixes do work....[/quote]
Also now:
(5) Shortcut "Singular (rxvt)" also runs Singular OK.
|
|
|
|
Posted: Wed Jul 26, 2006 3:06 am |
|
|
|
|
|
| |
Post subject: |
|
|
|
wienand wrote: Dear Mr Murray, ... you can do the following to use Singular and ESingular at least a bit more seamingless or at all: 1. Add the line Code: export PATH=/usr/local/bin:/usr/bin:/bin to the files /usr/bin/Singular and /usr/bin/ESingular. 2. Also add the line Code: export ESINGULAR_EMACS=/usr/bin/xemacs-21.4.19.exe to the file /usr/bin/ESingular. I can confirm that those fixes do work. More precisely: I assume that, because of the mount Code: V:cygwinbin on /usr/bin type system the files to be edited are actually the ones in in V:cygwinbin. I did add the export of ESINGULAR_EMACS to /usr/bin/ESingular. And in each of /usr/bin/Singular and /usr/bin/ESingular I inserted the line Code: export PATH=/usr/local/bin:/usr/bin:/bin immediately before the existing line: Code: export PATH="/usr/lib/Singular:$PATH" Now: (1) The command singular at the bash prompt does run OK (without, of course, my needing to use any export PATH... command first in bash. (2) Provided of course I first start x (e.g., using the batch file startxserver.bat from the supplied shortcut in the Singular CAS startup folder), the command ESingular at the bash prompt now also works. (3) The shortcut "Singular (Emacs)" after shortcut "Start X" also runs OK. (4) The shortcut "Singular (Emacs and X-Server) (experimental)" seems to do nothing useful: It does start bash.exe without any bash window opening, and bash.exe almost immediately closes. (I followed this through Sysinternals Process Explorer.) [quote="wienand"]Dear Mr Murray,
... you can do the following to use Singular and ESingular at least a bit more seamingless or at all:
1. Add the line
[code]export PATH=/usr/local/bin:/usr/bin:/bin[/code]
to the files [i]/usr/bin/Singular[/i] and [i]/usr/bin/ESingular[/i].
2. Also add the line
[code]export ESINGULAR_EMACS=/usr/bin/xemacs-21.4.19.exe[/code]
to the file [i]/usr/bin/ESingular[/i].
[/quote]
I can confirm that those fixes do work. More precisely:
I assume that, because of the mount
[code]V:cygwinbin on /usr/bin type system[/code]
the files to be edited are actually the ones in in [i]V:cygwinbin[/i].
I did add the export of [i]ESINGULAR_EMACS[/i] to [i]/usr/bin/ESingular[/i]. And in each of [i]/usr/bin/Singular[/i] and [i]/usr/bin/ESingular[/i] I inserted the line
[code]export PATH=/usr/local/bin:/usr/bin:/bin[/code]
immediately before the existing line:
[code]export PATH="/usr/lib/Singular:$PATH"[/code]
Now:
(1) The command [i]singular[/i] at the bash prompt does run OK (without, of course, my needing to use any [i]export PATH...[/i] command first in bash.
(2) Provided of course I first start x (e.g., using the batch file startxserver.bat from the supplied shortcut in the [i]Singular CAS[/i] startup folder), the command [i]ESingular[/i] at the bash prompt now also works.
(3) The shortcut "Singular (Emacs)" after shortcut "Start X" also runs OK.
(4) The shortcut "Singular (Emacs and X-Server) (experimental)" seems to do nothing useful: It does start [i]bash.exe[/i] without any bash window opening, and [i]bash.exe[/i] almost immediately closes. (I followed this through Sysinternals Process Explorer.)
|
|
|
|
Posted: Wed Jul 26, 2006 2:57 am |
|
|
|
|
|
| |
Post subject: |
|
|
|
Dear Mr Murray, I have investigated your problem further and can now reproduce the error. As soon as I copy your path to the path variable Singular crashes while starting. I have not figured out, what exactly causes the problem, but I will look into it further. Meanwhile you can do the following to use Singular and ESingular at least a bit more seamingless or at all: 1. Add the line Code: export PATH=/usr/local/bin:/usr/bin:/bin to the files /usr/bin/Singular and /usr/bin/ESingular. 2. Also add the line Code: export ESINGULAR_EMACS=/usr/bin/xemacs-21.4.19.exe to the file /usr/bin/ESingular. For some reason, the program forgets the first "/". I was not able to reproduce this behavior on my machine and if it works with setting the enviroment variable, I will postpone this problem after I solved the path issue. After these changes you should be able to use Singular and ESingular from every Cygwin terminal. Please report failure or hopefully success here or to singular at mathematik dot uni-kl dot de. Dear Mr Murray,
I have investigated your problem further and can now reproduce the error. As soon as I copy your path to the path variable Singular crashes while starting. I have not figured out, what exactly causes the problem, but I will look into it further. Meanwhile you can do the following to use Singular and ESingular at least a bit more seamingless or at all:
1. Add the line
[code]export PATH=/usr/local/bin:/usr/bin:/bin[/code]
to the files [i]/usr/bin/Singular[/i] and [i]/usr/bin/ESingular[/i].
2. Also add the line
[code]export ESINGULAR_EMACS=/usr/bin/xemacs-21.4.19.exe[/code]
to the file [i]/usr/bin/ESingular[/i].
For some reason, the program forgets the first "/". I was not able to reproduce this behavior on my machine and if it works with setting the enviroment variable, I will postpone this problem after I solved the path issue.
After these changes you should be able to use Singular and ESingular from every Cygwin terminal. Please report failure or hopefully success here or to singular at mathematik dot uni-kl dot de.
|
|
|
|
Posted: Wed Jul 26, 2006 12:53 am |
|
|
|
|
|
| |
Post subject: |
Re: segment fault |
|
|
murray wrote: Is that PATH correct for Singular 3.0.1-1? I just installed cygwin with Singular (after having to uninstall cygwin from a partition that was getting too full), and in the cygwin tree directory /usr/local/bin is totally empty. The Singular binaries are in /lib/Singular. Moreover, if I try
export PATH=/usr/local/bin:/usr/bin:/bin
I get messages from bash:
bash: /usr/bin: is a directory
bash: /bin: is a directory
Finally, singular is not working in any fashion whatsoever: at the bash shell prompt I get error:
Singular : signal 11 (v: 3001/2005111410):
Segment fault/Bus error occurred (r:1153607477)
This is after setting all the Windows environment variables to what they should be, I think -- in particular, using /lib/Singular (and NOT /usr/lib/Singular, which does not exist) for the value of SINGULAR_BIN_DIR.
I get the same type of error if I try to run singular in a Windows command prompt window. 1. I made a really silly mistake when I tried your diagnostic of exporting PATH from within cygwin: I erroneoulsy used semicolons instead of colons to separate paths. Now, if at the bash prompt I do correctly type export PATH=/usr/local/bin:/usr/bin:/bin then I CAN start Singular without error using command "singular". That's good! However, I still get the Segment fault... error if I do not export PATH. Executing "mount" at the bash prompt shows V:cygwinbin on /usr/bin type system V:cygwinlib on /usr/lib type system V:cygwin on / type system (binmode) along with entries of the form d: on /cygdrive/d type system (binmode,noumount) for each of my partitions. Here is an excerpt from my windows PATH variable: v:cygwinbin;v:cygwinusrbin;v:cygwinusrlocalbin;v:cygwinusrX11R6bin;v:cygwinlibsingular; (I looked at the entire path and see no unusual characters or syntactical errors in it, although of course such might still be there.) 2. Even after doing export PATH, trying to run ESingular from the bash prompt causes a pop-up window "ESingular.exe" with text: Error: Execution of /usr/bin/xemacs-21.4.19.exe -no-init-file -eval '(progn (setq singular-emacs-home-directory "/usr/share/Singular/emacs") (load-file "/usr/share/Singular/emacs/.emacs-singular ") (singular-other "/usr/lib/Singular/Singular.exe" "/cygdrive/e/Documents/CygwinHome/" (list ) "singular"))' 3. Still singular also stops with a Segment fault if I try to run itfrom a Windows command prompt. I do have the following Windows environment variables set: SINGULAR_BIN_DIR=/lib/Singular SINGULAR_CHM_FILE=/usr/share/doc/Singular-3.0.1/doc/Manual.chm SINGULAR_EXAMPLES_DIR= /usr/share/doc/Singular-3.0.1/examples SINGULAR_IDX_FILE=/usr/share/doc/Singular-3.0.1/doc/singular.idx SINGULAR_INFO_FILE=/usr/share/info/singular.info SINGULAR_ROOT_DIR=/usr/share/Singular [quote="murray"]
Is that PATH correct for Singular 3.0.1-1? I just installed cygwin with Singular (after having to uninstall cygwin from a partition that was getting too full), and in the cygwin tree directory /usr/local/bin is totally empty. The Singular binaries are in /lib/Singular. Moreover, if I try
export PATH=/usr/local/bin:/usr/bin:/bin
I get messages from bash:
bash: /usr/bin: is a directory
bash: /bin: is a directory
Finally, singular is not working in any fashion whatsoever: at the bash shell prompt I get error:
Singular : signal 11 (v: 3001/2005111410):
Segment fault/Bus error occurred (r:1153607477)
This is after setting all the Windows environment variables to what they should be, I think -- in particular, using /lib/Singular (and NOT /usr/lib/Singular, which does not exist) for the value of SINGULAR_BIN_DIR.
I get the same type of error if I try to run singular in a Windows command prompt window.[/quote]
1. I made a really silly mistake when I tried your diagnostic of exporting PATH from within cygwin: I erroneoulsy used semicolons instead of colons to separate paths. Now, if at the bash prompt I do correctly type
export PATH=/usr/local/bin:/usr/bin:/bin
then I CAN start Singular without error using command "singular". That's good!
However, I still get the Segment fault... error if I do not export PATH.
Executing "mount" at the bash prompt shows
V:cygwinbin on /usr/bin type system
V:cygwinlib on /usr/lib type system
V:cygwin on / type system (binmode)
along with entries of the form
d: on /cygdrive/d type system (binmode,noumount)
for each of my partitions.
Here is an excerpt from my windows PATH variable:
v:cygwinbin;v:cygwinusrbin;v:cygwinusrlocalbin;v:cygwinusrX11R6bin;v:cygwinlibsingular;
(I looked at the entire path and see no unusual characters or syntactical errors in it, although of course such might still be there.)
2. Even after doing export PATH, trying to run ESingular from the bash prompt causes a pop-up window "ESingular.exe" with text:
Error: Execution of
/usr/bin/xemacs-21.4.19.exe
-no-init-file
-eval '(progn (setq singular-emacs-home-directory
"/usr/share/Singular/emacs")
(load-file "/usr/share/Singular/emacs/.emacs-singular ")
(singular-other "/usr/lib/Singular/Singular.exe"
"/cygdrive/e/Documents/CygwinHome/" (list ) "singular"))'
3. Still singular also stops with a Segment fault if I try to run itfrom a Windows command prompt. I do have the following Windows environment variables set:
SINGULAR_BIN_DIR=/lib/Singular SINGULAR_CHM_FILE=/usr/share/doc/Singular-3.0.1/doc/Manual.chm
SINGULAR_EXAMPLES_DIR= /usr/share/doc/Singular-3.0.1/examples
SINGULAR_IDX_FILE=/usr/share/doc/Singular-3.0.1/doc/singular.idx
SINGULAR_INFO_FILE=/usr/share/info/singular.info
SINGULAR_ROOT_DIR=/usr/share/Singular
|
|
|
|
Posted: Tue Jul 25, 2006 8:33 pm |
|
|
|
|
|
| |
Post subject: |
|
|
|
It is hard to judge your problem. Can you please send the output of the following call inside a Cygwin terminal Code: cygcheck -s -r to Code: singular at mathematik dot uni-kl dot de The directory /usr/lib/Singular exists only as a POSIX path within Cygwin and not as a physical path on your hardrive. It is linked to the directoy Code: %CYGWIN HOME%/lib/Singular It is hard to judge your problem. Can you please send the output of the following call inside a Cygwin terminal
[code]cygcheck -s -r[/code]
to
[code]singular at mathematik dot uni-kl dot de[/code]
The directory /usr/lib/Singular exists only as a POSIX path within Cygwin and not as a physical path on your hardrive. It is linked to the directoy
[code]%CYGWIN HOME%/lib/Singular[/code]
|
|
|
|
Posted: Tue Jul 25, 2006 7:13 am |
|
|
|
|
|
| |
Post subject: |
s |
|
|
wienand wrote: Dear Singular users, the issue is resolved. The problem originated from an incorrect character in the path variable. You can try if this applies in your case in the following way: 1. Start a bash shell
2. export PATH=/usr/local/bin:/usr/bin:/bin
3. Singular or ESingular
If Singular is running fine after this, you can check the path variable for uncommon characters. Spaces are okay. To access the path variable please read: http://www.singular.uni-kl.de/forum/viewtopic.php?t=1475Sincerely, Oliver Wienand Windows Port Is that PATH correct for Singular 3.0.1-1? I just installed cygwin with Singular (after having to uninstall cygwin from a partition that was getting too full), and in the cygwin tree directory /usr/local/bin is totally empty. The Singular binaries are in /lib/Singular. Moreover, if I try export PATH=/usr/local/bin:/usr/bin:/bin I get messages from bash: bash: /usr/bin: is a directory bash: /bin: is a directory Finally, singular is not working in any fashion whatsoever: at the bash shell prompt I get error: Singular : signal 11 (v: 3001/2005111410): Segment fault/Bus error occurred (r:1153607477) This is after setting all the Windows environment variables to what they should be, I think -- in particular, using /lib/Singular (and NOT /usr/lib/Singular, which does not exist) for the value of SINGULAR_BIN_DIR. I get the same type of error if I try to run singular in a Windows command prompt window. [quote="wienand"]Dear Singular users,
the issue is resolved. The problem originated from an incorrect character in the path variable. You can try if this applies in your case in the following way:
[list]
1. Start a bash shell
2. export PATH=/usr/local/bin:/usr/bin:/bin
3. Singular or ESingular
[/list]
If Singular is running fine after this, you can check the path variable for uncommon characters. Spaces are okay. To access the path variable please read:
[url]http://www.singular.uni-kl.de/forum/viewtopic.php?t=1475[/url]
Sincerely,
Oliver Wienand
Windows Port[/quote]
Is that PATH correct for Singular 3.0.1-1? I just installed cygwin with Singular (after having to uninstall cygwin from a partition that was getting too full), and in the cygwin tree directory /usr/local/bin is totally empty. The Singular binaries are in /lib/Singular. Moreover, if I try
export PATH=/usr/local/bin:/usr/bin:/bin
I get messages from bash:
bash: /usr/bin: is a directory
bash: /bin: is a directory
Finally, singular is not working in any fashion whatsoever: at the bash shell prompt I get error:
Singular : signal 11 (v: 3001/2005111410):
Segment fault/Bus error occurred (r:1153607477)
This is after setting all the Windows environment variables to what they should be, I think -- in particular, using /lib/Singular (and NOT /usr/lib/Singular, which does not exist) for the value of SINGULAR_BIN_DIR.
I get the same type of error if I try to run singular in a Windows command prompt window.
|
|
|
|
Posted: Sun Jul 23, 2006 12:35 am |
|
|
|
|
|
| |
Post subject: |
|
|
|
wienand wrote: the issue is resolved.
Oliver Wienand
Windows Port Many thanks to Oliver Wienand for his patient intevention that resolved this problem! [quote="wienand"]
the issue is resolved.
Oliver Wienand
Windows Port[/quote]
Many thanks to Oliver Wienand for his patient intevention that resolved this problem!
|
|
|
|
Posted: Mon Jan 23, 2006 6:30 pm |
|
|
|
|
|
| |
Post subject: |
|
|
|
Dear Singular users, the issue is resolved. The problem originated from an incorrect character in the path variable. You can try if this applies in your case in the following way: 1. Start a bash shell
2. export PATH=/usr/local/bin:/usr/bin:/bin
3. Singular or ESingular
If Singular is running fine after this, you can check the path variable for uncommon characters. Spaces are okay. To access the path variable please read: http://www.singular.uni-kl.de/forum/viewtopic.php?t=1475Sincerely, Oliver Wienand Windows Port Dear Singular users,
the issue is resolved. The problem originated from an incorrect character in the path variable. You can try if this applies in your case in the following way:
[list]
1. Start a bash shell
2. export PATH=/usr/local/bin:/usr/bin:/bin
3. Singular or ESingular
[/list]
If Singular is running fine after this, you can check the path variable for uncommon characters. Spaces are okay. To access the path variable please read:
[url]http://www.singular.uni-kl.de/forum/viewtopic.php?t=1475[/url]
Sincerely,
Oliver Wienand
Windows Port
|
|
|
|
Posted: Mon Jan 23, 2006 5:59 pm |
|
|
|
|
|
| |
Post subject: |
status of Singular segment faults with cygwin |
|
|
wienand wrote: At first, to enable you to use Singular please read viewtopic.php?t=1475With this information you should be able to get a full functional Singular within the windows command shell you mentioned. To the bug itself I can also just refer to http://cygwin.com/problems.htmlOliver Wienand Singular Team OK, after following the instructions in the first (Singular) URL above, I CAN now get Singular to work by the following methods: 1. The Singular (Terminal) windows icon. 2. Any Windows command prompt. 3. In the Cygwin bash shell, typing command TSingular. On the other hand, I still CANNOT run Singular by the following methods: (a) In the Cygwin bash shell, typing command Singular: Segment fault/ Bus error (b) The Singular (rxvt) Windows icon (after starting X using the Start X- Server Windows icon): Segment fault/Bus error after the bash window opens. (c) The Singular (Emacs) Windows icon (after starting X using the Start X - Server Windows icon)): nothing seems to happen (d) In Cygwin, after giving command startx, in the Xterm window, typing command ESingular: Segmentation fault. The main problem is that I cannot run Singular with emacs. Upon a recommendation Larry Hall at Cygwin, I installed the latest Cygwin snapshot, but this does not fix anything with respect to Singular that I found broken before. [quote="wienand"]
At first, to enable you to use Singular please read
http://www.singular.uni-kl.de/forum/viewtopic.php?t=1475
With this information you should be able to get a full functional Singular within the windows command shell you mentioned.
To the bug itself I can also just refer to
http://cygwin.com/problems.html
Oliver Wienand
Singular Team[/quote]
OK, after following the instructions in the first (Singular) URL above, I CAN now get Singular to work by the following methods:
1. The Singular (Terminal) windows icon.
2. Any Windows command prompt.
3. In the Cygwin bash shell, typing command TSingular.
On the other hand, I still CANNOT run Singular by the following methods:
(a) In the Cygwin bash shell, typing command Singular: Segment fault/
Bus error
(b) The Singular (rxvt) Windows icon (after starting X using the Start X-
Server Windows icon): Segment fault/Bus error after the bash
window opens.
(c) The Singular (Emacs) Windows icon (after starting X using the Start
X - Server Windows icon)): nothing seems to happen
(d) In Cygwin, after giving command startx, in the Xterm window, typing
command ESingular: Segmentation fault.
The main problem is that I cannot run Singular with emacs.
Upon a recommendation Larry Hall at Cygwin, I installed the latest Cygwin snapshot, but this does not fix anything with respect to Singular that I found broken before.
|
|
|
|
Posted: Wed Jan 11, 2006 10:18 pm |
|
|
|
|
|
| |
Post subject: |
status of Singular segment faults with cygwin |
|
|
wienand wrote: At first, to enable you to use Singular please read viewtopic.php?t=1475With this information you should be able to get a full functional Singular within the windows command shell you mentioned. To the bug itself I can also just refer to http://cygwin.com/problems.htmlOliver Wienand Singular Team OK, after following the instructions in the first (Singular) URL above, I CAN now get Singular to work by the following methods: 1. The Singular (Terminal) windows icon. 2. Any Windows command prompt. 3. In the Cygwin bash shell, typing command TSingular. On the other hand, I still CANNOT run Singular by the following methods: (a) In the Cygwin bash shell, typing command Singular: Segment fault/ Bus error (b) The Singular (rxvt) Windows icon (after starting X using the Start X- Server Windows icon): Segment fault/Bus error after the bash window opens. (c) The Singular (Emacs) Windows icon (after starting X using the Start X - Server Windows icon)): nothing seems to happen (d) In Cygwin, after giving command startx, in the Xterm window, typing command ESingular: Segmentation fault. The main problem is that I cannot run Singular with emacs. Upon a recommendation Larry Hall at Cygwin, I installed the latest Cygwin snapshot, but this does not fix anything with respect to Singular that I found broken before. [quote="wienand"]
At first, to enable you to use Singular please read
http://www.singular.uni-kl.de/forum/viewtopic.php?t=1475
With this information you should be able to get a full functional Singular within the windows command shell you mentioned.
To the bug itself I can also just refer to
http://cygwin.com/problems.html
Oliver Wienand
Singular Team[/quote]
OK, after following the instructions in the first (Singular) URL above, I CAN now get Singular to work by the following methods:
1. The Singular (Terminal) windows icon.
2. Any Windows command prompt.
3. In the Cygwin bash shell, typing command TSingular.
On the other hand, I still CANNOT run Singular by the following methods:
(a) In the Cygwin bash shell, typing command Singular: Segment fault/
Bus error
(b) The Singular (rxvt) Windows icon (after starting X using the Start X-
Server Windows icon): Segment fault/Bus error after the bash
window opens.
(c) The Singular (Emacs) Windows icon (after starting X using the Start
X - Server Windows icon)): nothing seems to happen
(d) In Cygwin, after giving command startx, in the Xterm window, typing
command ESingular: Segmentation fault.
The main problem is that I cannot run Singular with emacs.
Upon a recommendation Larry Hall at Cygwin, I installed the latest Cygwin snapshot, but this does not fix anything with respect to Singular that I found broken before.
|
|
|
|
Posted: Wed Jan 11, 2006 10:17 pm |
|
|
|
|
|
| |
Post subject: |
|
|
|
Dear Mr. Eisenberg, Quote: On the other hand, if I go to the subdirectory libSingular of the main
cygwin directory and double-click Singular.exe, then Singular does run,
in a DOS command prompt window (although I see message "cannot open
`standard.lib'". At first, to enable you to use Singular please read viewtopic.php?t=1475With this information you should be able to get a full functional Singular within the windows command shell you mentioned. To the bug itself I can also just refer to http://cygwin.com/problems.htmlPlease apologize the delay of the answer, I was moving to the USA during the last week. Sincerely, Oliver Wienand Singular Team Dear Mr. Eisenberg,
[quote]On the other hand, if I go to the subdirectory libSingular of the main
cygwin directory and double-click Singular.exe, then Singular does run,
in a DOS command prompt window (although I see message "cannot open
`standard.lib'".[/quote]
At first, to enable you to use Singular please read
http://www.singular.uni-kl.de/forum/viewtopic.php?t=1475
With this information you should be able to get a full functional Singular within the windows command shell you mentioned.
To the bug itself I can also just refer to
http://cygwin.com/problems.html
Please apologize the delay of the answer, I was moving to the USA during the last week.
Sincerely,
Oliver Wienand
Singular Team
|
|
|
|
Posted: Tue Jan 10, 2006 5:59 am |
|
|
|
|
|
| |
Post subject: |
Singular 3.0.1-1 segment fault/Bus error with Cygwin |
|
|
|
In a new Cygwin installation (Cygwin dll version 1.5.18-1)-- under Windows XP Pro SP2 with all updates applied -- if I try to start Singular (version 3.0.1-1), I consistently get error:
Singular : signal 11 (v: 3001/2005111410):
Segment fault/Bus error occurred (r:1136570134)
Please inform the authors
trying to restart...
And Cygwin freezes.
I did submit a bug report but have had no feedback so far. I've tried uninsalling Cygwin entirely, including Singular, and re-installing from a new download (from a different mirror, even), but the same error persists.
In a new Cygwin installation (Cygwin dll version 1.5.18-1)-- under Windows XP Pro SP2 with all updates applied -- if I try to start Singular (version 3.0.1-1), I consistently get error:
Singular : signal 11 (v: 3001/2005111410):
Segment fault/Bus error occurred (r:1136570134)
Please inform the authors
trying to restart...
And Cygwin freezes.
I did submit a bug report but have had no feedback so far. I've tried uninsalling Cygwin entirely, including Singular, and re-installing from a new download (from a different mirror, even), but the same error persists.
|
|
|
|
Posted: Sun Jan 08, 2006 8:43 pm |
|
|
|
|
|
It is currently Fri May 13, 2022 10:59 am
|
|
Login
Register
Forum FAQ
Forum Search