From: SourceForge.net <no...@so...> - 2004-10-10 16:36:55
|
Bugs item #1044081, was opened at 2004-10-10 11:36 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 Category: msys Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Germán Méndez Bravo (kronuz) Assigned to: Earnie Boyd (earnie) Summary: Pagefault during ./configure execution. Initial Comment: Hello, I'm using MinGW-3.1.0-1, MSYS-1.0.10, and msysDTK-1.0.1 under Windows XP Pro SP2 and I some times get a nasty blue screen of death stating a PAGEFAULT_IN_NONPAGED_AREA (then I have to reset) when I'm using ./config.status generated by the GNU Autoconf 2.59. That's during the Makefile creation process. Since the problem happens only at some point during the execution of ./config.status (I never ever have had that problem before and no other app nor at some other point has the problem ever presented) Im guessing theres either a bug on the shell or on a program ran by ./config.status (somewhere between two config.status:xxx:creating /.../Makefile messages) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 |
From: SourceForge.net <no...@so...> - 2004-10-11 05:12:55
|
Bugs item #1044081, was opened at 2004-10-11 00:36 Message generated for change (Comment added) made by infidel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 Category: msys Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Germán Méndez Bravo (kronuz) Assigned to: Earnie Boyd (earnie) Summary: Pagefault during ./configure execution. Initial Comment: Hello, I'm using MinGW-3.1.0-1, MSYS-1.0.10, and msysDTK-1.0.1 under Windows XP Pro SP2 and I some times get a nasty blue screen of death stating a PAGEFAULT_IN_NONPAGED_AREA (then I have to reset) when I'm using ./config.status generated by the GNU Autoconf 2.59. That's during the Makefile creation process. Since the problem happens only at some point during the execution of ./config.status (I never ever have had that problem before and no other app nor at some other point has the problem ever presented) Im guessing theres either a bug on the shell or on a program ran by ./config.status (somewhere between two config.status:xxx:creating /.../Makefile messages) ---------------------------------------------------------------------- >Comment By: Luke Dunstan (infidel) Date: 2004-10-11 13:12 Message: Logged In: YES user_id=30442 I am pretty sure that a blue screen like that can only be caused by a driver problem, not by a user application like MSYS/MinGW. Is this problem repeatable? If you have any anti-virus software running, you might try disabling it to see if that is causing the problem. Does Windows give you any indication of which driver caused the fault? If not, you might try debugging the configure script to find which line is causing the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 |
From: SourceForge.net <no...@so...> - 2004-10-11 18:56:49
|
Bugs item #1044081, was opened at 2004-10-10 11:36 Message generated for change (Comment added) made by kronuz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 Category: msys Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Germán Méndez Bravo (kronuz) Assigned to: Earnie Boyd (earnie) Summary: Pagefault during ./configure execution. Initial Comment: Hello, I'm using MinGW-3.1.0-1, MSYS-1.0.10, and msysDTK-1.0.1 under Windows XP Pro SP2 and I some times get a nasty blue screen of death stating a PAGEFAULT_IN_NONPAGED_AREA (then I have to reset) when I'm using ./config.status generated by the GNU Autoconf 2.59. That's during the Makefile creation process. Since the problem happens only at some point during the execution of ./config.status (I never ever have had that problem before and no other app nor at some other point has the problem ever presented) Im guessing theres either a bug on the shell or on a program ran by ./config.status (somewhere between two config.status:xxx:creating /.../Makefile messages) ---------------------------------------------------------------------- >Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-11 13:56 Message: Logged In: YES user_id=218084 I have this problem almost every time I use ./config.status (but some times it runs okay) also, although the problem seems to always be somewhere between two config.status:xxx:creating /.../Makefile messages, it is not always between the same two Makefiles (for the same ./config.status) Windows doesn't give me any further information, but that it's a pagefault in a nonpaged area. I tried to find what line in the script was causing the problem, but sincerely, I couldn't find a way to do it. I tried to find a way to write in a file each line number being about to be executed, and in that way, after the crash, I could go to that file and see what the last line to be executed was, but I didnt know how to do it. I tried echos, but ./config.status is a big script, and it's a little hard for me to understand. The problem is weird, because it's always during config.satatus execution under MSYS and no other program has ever caused anything like that. Also my computer has been running fine for months in a very stable way with no problem whatsoever other than this. I don't have an overclocked machine and I have tested the hard drive, and the memory for errors several times with not a single problem found. ---------------------------------------------------------------------- Comment By: Luke Dunstan (infidel) Date: 2004-10-11 00:12 Message: Logged In: YES user_id=30442 I am pretty sure that a blue screen like that can only be caused by a driver problem, not by a user application like MSYS/MinGW. Is this problem repeatable? If you have any anti-virus software running, you might try disabling it to see if that is causing the problem. Does Windows give you any indication of which driver caused the fault? If not, you might try debugging the configure script to find which line is causing the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 |
From: SourceForge.net <no...@so...> - 2004-10-11 23:26:30
|
Bugs item #1044081, was opened at 2004-10-10 12:36 Message generated for change (Comment added) made by earnie You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 Category: msys Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Germán Méndez Bravo (kronuz) Assigned to: Earnie Boyd (earnie) Summary: Pagefault during ./configure execution. Initial Comment: Hello, I'm using MinGW-3.1.0-1, MSYS-1.0.10, and msysDTK-1.0.1 under Windows XP Pro SP2 and I some times get a nasty blue screen of death stating a PAGEFAULT_IN_NONPAGED_AREA (then I have to reset) when I'm using ./config.status generated by the GNU Autoconf 2.59. That's during the Makefile creation process. Since the problem happens only at some point during the execution of ./config.status (I never ever have had that problem before and no other app nor at some other point has the problem ever presented) Im guessing theres either a bug on the shell or on a program ran by ./config.status (somewhere between two config.status:xxx:creating /.../Makefile messages) ---------------------------------------------------------------------- >Comment By: Earnie Boyd (earnie) Date: 2004-10-11 19:26 Message: Logged In: YES user_id=15438 What is the package you are trying to build? What is the output of ``msysinfo all''? You should try the MSYS-1.0.11 snapshot to see if the problem still exists. ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-11 14:56 Message: Logged In: YES user_id=218084 I have this problem almost every time I use ./config.status (but some times it runs okay) also, although the problem seems to always be somewhere between two config.status:xxx:creating /.../Makefile messages, it is not always between the same two Makefiles (for the same ./config.status) Windows doesn't give me any further information, but that it's a pagefault in a nonpaged area. I tried to find what line in the script was causing the problem, but sincerely, I couldn't find a way to do it. I tried to find a way to write in a file each line number being about to be executed, and in that way, after the crash, I could go to that file and see what the last line to be executed was, but I didnt know how to do it. I tried echos, but ./config.status is a big script, and it's a little hard for me to understand. The problem is weird, because it's always during config.satatus execution under MSYS and no other program has ever caused anything like that. Also my computer has been running fine for months in a very stable way with no problem whatsoever other than this. I don't have an overclocked machine and I have tested the hard drive, and the memory for errors several times with not a single problem found. ---------------------------------------------------------------------- Comment By: Luke Dunstan (infidel) Date: 2004-10-11 01:12 Message: Logged In: YES user_id=30442 I am pretty sure that a blue screen like that can only be caused by a driver problem, not by a user application like MSYS/MinGW. Is this problem repeatable? If you have any anti-virus software running, you might try disabling it to see if that is causing the problem. Does Windows give you any indication of which driver caused the fault? If not, you might try debugging the configure script to find which line is causing the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 |
From: SourceForge.net <no...@so...> - 2004-10-12 16:53:17
|
Bugs item #1044081, was opened at 2004-10-10 11:36 Message generated for change (Comment added) made by kronuz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 Category: msys Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Germán Méndez Bravo (kronuz) Assigned to: Earnie Boyd (earnie) Summary: Pagefault during ./configure execution. Initial Comment: Hello, I'm using MinGW-3.1.0-1, MSYS-1.0.10, and msysDTK-1.0.1 under Windows XP Pro SP2 and I some times get a nasty blue screen of death stating a PAGEFAULT_IN_NONPAGED_AREA (then I have to reset) when I'm using ./config.status generated by the GNU Autoconf 2.59. That's during the Makefile creation process. Since the problem happens only at some point during the execution of ./config.status (I never ever have had that problem before and no other app nor at some other point has the problem ever presented) Im guessing theres either a bug on the shell or on a program ran by ./config.status (somewhere between two config.status:xxx:creating /.../Makefile messages) ---------------------------------------------------------------------- >Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-12 11:53 Message: Logged In: YES user_id=218084 I have tried with several packages and I have had the problem with all of them. (some times it works, but not always.) Currently I was trying to compile the SDL 1.2.7 package, but the problem has been there with others. I'll get the MSYS-1.0.11 snapshot right now and I'll let you know the results, in the mean time I have attached the msysinfo stuff. ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-11 18:26 Message: Logged In: YES user_id=15438 What is the package you are trying to build? What is the output of ``msysinfo all''? You should try the MSYS-1.0.11 snapshot to see if the problem still exists. ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-11 13:56 Message: Logged In: YES user_id=218084 I have this problem almost every time I use ./config.status (but some times it runs okay) also, although the problem seems to always be somewhere between two config.status:xxx:creating /.../Makefile messages, it is not always between the same two Makefiles (for the same ./config.status) Windows doesn't give me any further information, but that it's a pagefault in a nonpaged area. I tried to find what line in the script was causing the problem, but sincerely, I couldn't find a way to do it. I tried to find a way to write in a file each line number being about to be executed, and in that way, after the crash, I could go to that file and see what the last line to be executed was, but I didnt know how to do it. I tried echos, but ./config.status is a big script, and it's a little hard for me to understand. The problem is weird, because it's always during config.satatus execution under MSYS and no other program has ever caused anything like that. Also my computer has been running fine for months in a very stable way with no problem whatsoever other than this. I don't have an overclocked machine and I have tested the hard drive, and the memory for errors several times with not a single problem found. ---------------------------------------------------------------------- Comment By: Luke Dunstan (infidel) Date: 2004-10-11 00:12 Message: Logged In: YES user_id=30442 I am pretty sure that a blue screen like that can only be caused by a driver problem, not by a user application like MSYS/MinGW. Is this problem repeatable? If you have any anti-virus software running, you might try disabling it to see if that is causing the problem. Does Windows give you any indication of which driver caused the fault? If not, you might try debugging the configure script to find which line is causing the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 |
From: SourceForge.net <no...@so...> - 2004-10-12 23:39:46
|
Bugs item #1044081, was opened at 2004-10-10 12:36 Message generated for change (Comment added) made by earnie You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 Category: msys Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Germán Méndez Bravo (kronuz) Assigned to: Earnie Boyd (earnie) Summary: Pagefault during ./configure execution. Initial Comment: Hello, I'm using MinGW-3.1.0-1, MSYS-1.0.10, and msysDTK-1.0.1 under Windows XP Pro SP2 and I some times get a nasty blue screen of death stating a PAGEFAULT_IN_NONPAGED_AREA (then I have to reset) when I'm using ./config.status generated by the GNU Autoconf 2.59. That's during the Makefile creation process. Since the problem happens only at some point during the execution of ./config.status (I never ever have had that problem before and no other app nor at some other point has the problem ever presented) Im guessing theres either a bug on the shell or on a program ran by ./config.status (somewhere between two config.status:xxx:creating /.../Makefile messages) ---------------------------------------------------------------------- >Comment By: Earnie Boyd (earnie) Date: 2004-10-12 19:39 Message: Logged In: YES user_id=15438 I don't see anything wrong. I know that there is a memory recall due to strange lockups and data loss but I don't know the details on that yet. I know that my COMPAQ Evo N610c laptop is affected by the recall. However, I don't have problems building programs with blue screens of death. Is there possibly a cygwin1.dll on your path that is used by some potential executable that the config.status process might use? Earnie ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-12 12:53 Message: Logged In: YES user_id=218084 I have tried with several packages and I have had the problem with all of them. (some times it works, but not always.) Currently I was trying to compile the SDL 1.2.7 package, but the problem has been there with others. I'll get the MSYS-1.0.11 snapshot right now and I'll let you know the results, in the mean time I have attached the msysinfo stuff. ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-11 19:26 Message: Logged In: YES user_id=15438 What is the package you are trying to build? What is the output of ``msysinfo all''? You should try the MSYS-1.0.11 snapshot to see if the problem still exists. ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-11 14:56 Message: Logged In: YES user_id=218084 I have this problem almost every time I use ./config.status (but some times it runs okay) also, although the problem seems to always be somewhere between two config.status:xxx:creating /.../Makefile messages, it is not always between the same two Makefiles (for the same ./config.status) Windows doesn't give me any further information, but that it's a pagefault in a nonpaged area. I tried to find what line in the script was causing the problem, but sincerely, I couldn't find a way to do it. I tried to find a way to write in a file each line number being about to be executed, and in that way, after the crash, I could go to that file and see what the last line to be executed was, but I didnt know how to do it. I tried echos, but ./config.status is a big script, and it's a little hard for me to understand. The problem is weird, because it's always during config.satatus execution under MSYS and no other program has ever caused anything like that. Also my computer has been running fine for months in a very stable way with no problem whatsoever other than this. I don't have an overclocked machine and I have tested the hard drive, and the memory for errors several times with not a single problem found. ---------------------------------------------------------------------- Comment By: Luke Dunstan (infidel) Date: 2004-10-11 01:12 Message: Logged In: YES user_id=30442 I am pretty sure that a blue screen like that can only be caused by a driver problem, not by a user application like MSYS/MinGW. Is this problem repeatable? If you have any anti-virus software running, you might try disabling it to see if that is causing the problem. Does Windows give you any indication of which driver caused the fault? If not, you might try debugging the configure script to find which line is causing the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 |
From: SourceForge.net <no...@so...> - 2004-10-13 16:56:42
|
Bugs item #1044081, was opened at 2004-10-10 11:36 Message generated for change (Comment added) made by kronuz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 Category: msys Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Germán Méndez Bravo (kronuz) Assigned to: Earnie Boyd (earnie) Summary: Pagefault during ./configure execution. Initial Comment: Hello, I'm using MinGW-3.1.0-1, MSYS-1.0.10, and msysDTK-1.0.1 under Windows XP Pro SP2 and I some times get a nasty blue screen of death stating a PAGEFAULT_IN_NONPAGED_AREA (then I have to reset) when I'm using ./config.status generated by the GNU Autoconf 2.59. That's during the Makefile creation process. Since the problem happens only at some point during the execution of ./config.status (I never ever have had that problem before and no other app nor at some other point has the problem ever presented) Im guessing theres either a bug on the shell or on a program ran by ./config.status (somewhere between two config.status:xxx:creating /.../Makefile messages) ---------------------------------------------------------------------- >Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-13 11:56 Message: Logged In: YES user_id=218084 Nope, I'm not using cygwin... I got the snapshot tou told me about, and it looked like the problem was gone, but after only a few ./config.status runs.... It seems now is just not that often that it crashes, but during the compilation of about 15 different packages, it crashed twice (blue screen). Do you know what can I do to trace the problematic line in the ./config.status? Thanks, Kronuz ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-12 18:39 Message: Logged In: YES user_id=15438 I don't see anything wrong. I know that there is a memory recall due to strange lockups and data loss but I don't know the details on that yet. I know that my COMPAQ Evo N610c laptop is affected by the recall. However, I don't have problems building programs with blue screens of death. Is there possibly a cygwin1.dll on your path that is used by some potential executable that the config.status process might use? Earnie ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-12 11:53 Message: Logged In: YES user_id=218084 I have tried with several packages and I have had the problem with all of them. (some times it works, but not always.) Currently I was trying to compile the SDL 1.2.7 package, but the problem has been there with others. I'll get the MSYS-1.0.11 snapshot right now and I'll let you know the results, in the mean time I have attached the msysinfo stuff. ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-11 18:26 Message: Logged In: YES user_id=15438 What is the package you are trying to build? What is the output of ``msysinfo all''? You should try the MSYS-1.0.11 snapshot to see if the problem still exists. ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-11 13:56 Message: Logged In: YES user_id=218084 I have this problem almost every time I use ./config.status (but some times it runs okay) also, although the problem seems to always be somewhere between two config.status:xxx:creating /.../Makefile messages, it is not always between the same two Makefiles (for the same ./config.status) Windows doesn't give me any further information, but that it's a pagefault in a nonpaged area. I tried to find what line in the script was causing the problem, but sincerely, I couldn't find a way to do it. I tried to find a way to write in a file each line number being about to be executed, and in that way, after the crash, I could go to that file and see what the last line to be executed was, but I didnt know how to do it. I tried echos, but ./config.status is a big script, and it's a little hard for me to understand. The problem is weird, because it's always during config.satatus execution under MSYS and no other program has ever caused anything like that. Also my computer has been running fine for months in a very stable way with no problem whatsoever other than this. I don't have an overclocked machine and I have tested the hard drive, and the memory for errors several times with not a single problem found. ---------------------------------------------------------------------- Comment By: Luke Dunstan (infidel) Date: 2004-10-11 00:12 Message: Logged In: YES user_id=30442 I am pretty sure that a blue screen like that can only be caused by a driver problem, not by a user application like MSYS/MinGW. Is this problem repeatable? If you have any anti-virus software running, you might try disabling it to see if that is causing the problem. Does Windows give you any indication of which driver caused the fault? If not, you might try debugging the configure script to find which line is causing the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 |
From: SourceForge.net <no...@so...> - 2004-10-14 00:21:26
|
Bugs item #1044081, was opened at 2004-10-10 12:36 Message generated for change (Comment added) made by earnie You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 Category: msys Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Germán Méndez Bravo (kronuz) Assigned to: Earnie Boyd (earnie) Summary: Pagefault during ./configure execution. Initial Comment: Hello, I'm using MinGW-3.1.0-1, MSYS-1.0.10, and msysDTK-1.0.1 under Windows XP Pro SP2 and I some times get a nasty blue screen of death stating a PAGEFAULT_IN_NONPAGED_AREA (then I have to reset) when I'm using ./config.status generated by the GNU Autoconf 2.59. That's during the Makefile creation process. Since the problem happens only at some point during the execution of ./config.status (I never ever have had that problem before and no other app nor at some other point has the problem ever presented) Im guessing theres either a bug on the shell or on a program ran by ./config.status (somewhere between two config.status:xxx:creating /.../Makefile messages) ---------------------------------------------------------------------- >Comment By: Earnie Boyd (earnie) Date: 2004-10-13 20:21 Message: Logged In: YES user_id=15438 If you're lucky it maybe in the config.log file. You can use ``sh -x ./config.status'' to watch the script commands. Earnie ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-13 12:56 Message: Logged In: YES user_id=218084 Nope, I'm not using cygwin... I got the snapshot tou told me about, and it looked like the problem was gone, but after only a few ./config.status runs.... It seems now is just not that often that it crashes, but during the compilation of about 15 different packages, it crashed twice (blue screen). Do you know what can I do to trace the problematic line in the ./config.status? Thanks, Kronuz ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-12 19:39 Message: Logged In: YES user_id=15438 I don't see anything wrong. I know that there is a memory recall due to strange lockups and data loss but I don't know the details on that yet. I know that my COMPAQ Evo N610c laptop is affected by the recall. However, I don't have problems building programs with blue screens of death. Is there possibly a cygwin1.dll on your path that is used by some potential executable that the config.status process might use? Earnie ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-12 12:53 Message: Logged In: YES user_id=218084 I have tried with several packages and I have had the problem with all of them. (some times it works, but not always.) Currently I was trying to compile the SDL 1.2.7 package, but the problem has been there with others. I'll get the MSYS-1.0.11 snapshot right now and I'll let you know the results, in the mean time I have attached the msysinfo stuff. ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-11 19:26 Message: Logged In: YES user_id=15438 What is the package you are trying to build? What is the output of ``msysinfo all''? You should try the MSYS-1.0.11 snapshot to see if the problem still exists. ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-11 14:56 Message: Logged In: YES user_id=218084 I have this problem almost every time I use ./config.status (but some times it runs okay) also, although the problem seems to always be somewhere between two config.status:xxx:creating /.../Makefile messages, it is not always between the same two Makefiles (for the same ./config.status) Windows doesn't give me any further information, but that it's a pagefault in a nonpaged area. I tried to find what line in the script was causing the problem, but sincerely, I couldn't find a way to do it. I tried to find a way to write in a file each line number being about to be executed, and in that way, after the crash, I could go to that file and see what the last line to be executed was, but I didnt know how to do it. I tried echos, but ./config.status is a big script, and it's a little hard for me to understand. The problem is weird, because it's always during config.satatus execution under MSYS and no other program has ever caused anything like that. Also my computer has been running fine for months in a very stable way with no problem whatsoever other than this. I don't have an overclocked machine and I have tested the hard drive, and the memory for errors several times with not a single problem found. ---------------------------------------------------------------------- Comment By: Luke Dunstan (infidel) Date: 2004-10-11 01:12 Message: Logged In: YES user_id=30442 I am pretty sure that a blue screen like that can only be caused by a driver problem, not by a user application like MSYS/MinGW. Is this problem repeatable? If you have any anti-virus software running, you might try disabling it to see if that is causing the problem. Does Windows give you any indication of which driver caused the fault? If not, you might try debugging the configure script to find which line is causing the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 |
From: SourceForge.net <no...@so...> - 2004-10-14 00:31:57
|
Bugs item #1044081, was opened at 2004-10-10 12:36 Message generated for change (Comment added) made by earnie You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 Category: msys Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Germán Méndez Bravo (kronuz) Assigned to: Earnie Boyd (earnie) Summary: Pagefault during ./configure execution. Initial Comment: Hello, I'm using MinGW-3.1.0-1, MSYS-1.0.10, and msysDTK-1.0.1 under Windows XP Pro SP2 and I some times get a nasty blue screen of death stating a PAGEFAULT_IN_NONPAGED_AREA (then I have to reset) when I'm using ./config.status generated by the GNU Autoconf 2.59. That's during the Makefile creation process. Since the problem happens only at some point during the execution of ./config.status (I never ever have had that problem before and no other app nor at some other point has the problem ever presented) Im guessing theres either a bug on the shell or on a program ran by ./config.status (somewhere between two config.status:xxx:creating /.../Makefile messages) ---------------------------------------------------------------------- >Comment By: Earnie Boyd (earnie) Date: 2004-10-13 20:31 Message: Logged In: YES user_id=15438 BTW, just because you haven't installed Cygwin, other things you've installed may have installed a cygwin1.dll, including proprietary software you paid for. Earnie ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-13 20:21 Message: Logged In: YES user_id=15438 If you're lucky it maybe in the config.log file. You can use ``sh -x ./config.status'' to watch the script commands. Earnie ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-13 12:56 Message: Logged In: YES user_id=218084 Nope, I'm not using cygwin... I got the snapshot tou told me about, and it looked like the problem was gone, but after only a few ./config.status runs.... It seems now is just not that often that it crashes, but during the compilation of about 15 different packages, it crashed twice (blue screen). Do you know what can I do to trace the problematic line in the ./config.status? Thanks, Kronuz ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-12 19:39 Message: Logged In: YES user_id=15438 I don't see anything wrong. I know that there is a memory recall due to strange lockups and data loss but I don't know the details on that yet. I know that my COMPAQ Evo N610c laptop is affected by the recall. However, I don't have problems building programs with blue screens of death. Is there possibly a cygwin1.dll on your path that is used by some potential executable that the config.status process might use? Earnie ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-12 12:53 Message: Logged In: YES user_id=218084 I have tried with several packages and I have had the problem with all of them. (some times it works, but not always.) Currently I was trying to compile the SDL 1.2.7 package, but the problem has been there with others. I'll get the MSYS-1.0.11 snapshot right now and I'll let you know the results, in the mean time I have attached the msysinfo stuff. ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-11 19:26 Message: Logged In: YES user_id=15438 What is the package you are trying to build? What is the output of ``msysinfo all''? You should try the MSYS-1.0.11 snapshot to see if the problem still exists. ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-11 14:56 Message: Logged In: YES user_id=218084 I have this problem almost every time I use ./config.status (but some times it runs okay) also, although the problem seems to always be somewhere between two config.status:xxx:creating /.../Makefile messages, it is not always between the same two Makefiles (for the same ./config.status) Windows doesn't give me any further information, but that it's a pagefault in a nonpaged area. I tried to find what line in the script was causing the problem, but sincerely, I couldn't find a way to do it. I tried to find a way to write in a file each line number being about to be executed, and in that way, after the crash, I could go to that file and see what the last line to be executed was, but I didnt know how to do it. I tried echos, but ./config.status is a big script, and it's a little hard for me to understand. The problem is weird, because it's always during config.satatus execution under MSYS and no other program has ever caused anything like that. Also my computer has been running fine for months in a very stable way with no problem whatsoever other than this. I don't have an overclocked machine and I have tested the hard drive, and the memory for errors several times with not a single problem found. ---------------------------------------------------------------------- Comment By: Luke Dunstan (infidel) Date: 2004-10-11 01:12 Message: Logged In: YES user_id=30442 I am pretty sure that a blue screen like that can only be caused by a driver problem, not by a user application like MSYS/MinGW. Is this problem repeatable? If you have any anti-virus software running, you might try disabling it to see if that is causing the problem. Does Windows give you any indication of which driver caused the fault? If not, you might try debugging the configure script to find which line is causing the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 |
From: SourceForge.net <no...@so...> - 2004-10-24 16:07:56
|
Bugs item #1044081, was opened at 2004-10-10 18:36 Message generated for change (Comment added) made by johan-boule You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 Category: msys Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Germán Méndez Bravo (kronuz) Assigned to: Earnie Boyd (earnie) Summary: Pagefault during ./configure execution. Initial Comment: Hello, I'm using MinGW-3.1.0-1, MSYS-1.0.10, and msysDTK-1.0.1 under Windows XP Pro SP2 and I some times get a nasty blue screen of death stating a PAGEFAULT_IN_NONPAGED_AREA (then I have to reset) when I'm using ./config.status generated by the GNU Autoconf 2.59. That's during the Makefile creation process. Since the problem happens only at some point during the execution of ./config.status (I never ever have had that problem before and no other app nor at some other point has the problem ever presented) Im guessing theres either a bug on the shell or on a program ran by ./config.status (somewhere between two config.status:xxx:creating /.../Makefile messages) ---------------------------------------------------------------------- Comment By: Johan Boulé (johan-boule) Date: 2004-10-24 18:07 Message: Logged In: YES user_id=96100 Have you run a memory test with the "memtest86" program? ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-14 02:31 Message: Logged In: YES user_id=15438 BTW, just because you haven't installed Cygwin, other things you've installed may have installed a cygwin1.dll, including proprietary software you paid for. Earnie ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-14 02:21 Message: Logged In: YES user_id=15438 If you're lucky it maybe in the config.log file. You can use ``sh -x ./config.status'' to watch the script commands. Earnie ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-13 18:56 Message: Logged In: YES user_id=218084 Nope, I'm not using cygwin... I got the snapshot tou told me about, and it looked like the problem was gone, but after only a few ./config.status runs.... It seems now is just not that often that it crashes, but during the compilation of about 15 different packages, it crashed twice (blue screen). Do you know what can I do to trace the problematic line in the ./config.status? Thanks, Kronuz ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-13 01:39 Message: Logged In: YES user_id=15438 I don't see anything wrong. I know that there is a memory recall due to strange lockups and data loss but I don't know the details on that yet. I know that my COMPAQ Evo N610c laptop is affected by the recall. However, I don't have problems building programs with blue screens of death. Is there possibly a cygwin1.dll on your path that is used by some potential executable that the config.status process might use? Earnie ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-12 18:53 Message: Logged In: YES user_id=218084 I have tried with several packages and I have had the problem with all of them. (some times it works, but not always.) Currently I was trying to compile the SDL 1.2.7 package, but the problem has been there with others. I'll get the MSYS-1.0.11 snapshot right now and I'll let you know the results, in the mean time I have attached the msysinfo stuff. ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-12 01:26 Message: Logged In: YES user_id=15438 What is the package you are trying to build? What is the output of ``msysinfo all''? You should try the MSYS-1.0.11 snapshot to see if the problem still exists. ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-11 20:56 Message: Logged In: YES user_id=218084 I have this problem almost every time I use ./config.status (but some times it runs okay) also, although the problem seems to always be somewhere between two config.status:xxx:creating /.../Makefile messages, it is not always between the same two Makefiles (for the same ./config.status) Windows doesn't give me any further information, but that it's a pagefault in a nonpaged area. I tried to find what line in the script was causing the problem, but sincerely, I couldn't find a way to do it. I tried to find a way to write in a file each line number being about to be executed, and in that way, after the crash, I could go to that file and see what the last line to be executed was, but I didnt know how to do it. I tried echos, but ./config.status is a big script, and it's a little hard for me to understand. The problem is weird, because it's always during config.satatus execution under MSYS and no other program has ever caused anything like that. Also my computer has been running fine for months in a very stable way with no problem whatsoever other than this. I don't have an overclocked machine and I have tested the hard drive, and the memory for errors several times with not a single problem found. ---------------------------------------------------------------------- Comment By: Luke Dunstan (infidel) Date: 2004-10-11 07:12 Message: Logged In: YES user_id=30442 I am pretty sure that a blue screen like that can only be caused by a driver problem, not by a user application like MSYS/MinGW. Is this problem repeatable? If you have any anti-virus software running, you might try disabling it to see if that is causing the problem. Does Windows give you any indication of which driver caused the fault? If not, you might try debugging the configure script to find which line is causing the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 |
From: SourceForge.net <no...@so...> - 2004-10-24 19:04:36
|
Bugs item #1044081, was opened at 2004-10-10 11:36 Message generated for change (Comment added) made by kronuz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 Category: msys Group: Unreproducible Status: Open Resolution: None Priority: 5 Submitted By: Germán Méndez Bravo (kronuz) Assigned to: Earnie Boyd (earnie) Summary: Pagefault during ./configure execution. Initial Comment: Hello, I'm using MinGW-3.1.0-1, MSYS-1.0.10, and msysDTK-1.0.1 under Windows XP Pro SP2 and I some times get a nasty blue screen of death stating a PAGEFAULT_IN_NONPAGED_AREA (then I have to reset) when I'm using ./config.status generated by the GNU Autoconf 2.59. That's during the Makefile creation process. Since the problem happens only at some point during the execution of ./config.status (I never ever have had that problem before and no other app nor at some other point has the problem ever presented) Im guessing theres either a bug on the shell or on a program ran by ./config.status (somewhere between two config.status:xxx:creating /.../Makefile messages) ---------------------------------------------------------------------- >Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-24 14:04 Message: Logged In: YES user_id=218084 Nope, I'm positive I didn't have any cygwin stuff installed. This is getting weird, I'm guessing nobody else has reported this problem... but the weird thing is that this problem only shows up during ./config.status execution, only under MinGW... I have tested my memory using memtest86 and the microsoft memory tester too, with no problems whatsoever. Also, I have tested my drives for bad sectors, but nothing seems wrong. ---------------------------------------------------------------------- Comment By: Johan Boulé (johan-boule) Date: 2004-10-24 11:07 Message: Logged In: YES user_id=96100 Have you run a memory test with the "memtest86" program? ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-13 19:31 Message: Logged In: YES user_id=15438 BTW, just because you haven't installed Cygwin, other things you've installed may have installed a cygwin1.dll, including proprietary software you paid for. Earnie ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-13 19:21 Message: Logged In: YES user_id=15438 If you're lucky it maybe in the config.log file. You can use ``sh -x ./config.status'' to watch the script commands. Earnie ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-13 11:56 Message: Logged In: YES user_id=218084 Nope, I'm not using cygwin... I got the snapshot tou told me about, and it looked like the problem was gone, but after only a few ./config.status runs.... It seems now is just not that often that it crashes, but during the compilation of about 15 different packages, it crashed twice (blue screen). Do you know what can I do to trace the problematic line in the ./config.status? Thanks, Kronuz ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-12 18:39 Message: Logged In: YES user_id=15438 I don't see anything wrong. I know that there is a memory recall due to strange lockups and data loss but I don't know the details on that yet. I know that my COMPAQ Evo N610c laptop is affected by the recall. However, I don't have problems building programs with blue screens of death. Is there possibly a cygwin1.dll on your path that is used by some potential executable that the config.status process might use? Earnie ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-12 11:53 Message: Logged In: YES user_id=218084 I have tried with several packages and I have had the problem with all of them. (some times it works, but not always.) Currently I was trying to compile the SDL 1.2.7 package, but the problem has been there with others. I'll get the MSYS-1.0.11 snapshot right now and I'll let you know the results, in the mean time I have attached the msysinfo stuff. ---------------------------------------------------------------------- Comment By: Earnie Boyd (earnie) Date: 2004-10-11 18:26 Message: Logged In: YES user_id=15438 What is the package you are trying to build? What is the output of ``msysinfo all''? You should try the MSYS-1.0.11 snapshot to see if the problem still exists. ---------------------------------------------------------------------- Comment By: Germán Méndez Bravo (kronuz) Date: 2004-10-11 13:56 Message: Logged In: YES user_id=218084 I have this problem almost every time I use ./config.status (but some times it runs okay) also, although the problem seems to always be somewhere between two config.status:xxx:creating /.../Makefile messages, it is not always between the same two Makefiles (for the same ./config.status) Windows doesn't give me any further information, but that it's a pagefault in a nonpaged area. I tried to find what line in the script was causing the problem, but sincerely, I couldn't find a way to do it. I tried to find a way to write in a file each line number being about to be executed, and in that way, after the crash, I could go to that file and see what the last line to be executed was, but I didnt know how to do it. I tried echos, but ./config.status is a big script, and it's a little hard for me to understand. The problem is weird, because it's always during config.satatus execution under MSYS and no other program has ever caused anything like that. Also my computer has been running fine for months in a very stable way with no problem whatsoever other than this. I don't have an overclocked machine and I have tested the hard drive, and the memory for errors several times with not a single problem found. ---------------------------------------------------------------------- Comment By: Luke Dunstan (infidel) Date: 2004-10-11 00:12 Message: Logged In: YES user_id=30442 I am pretty sure that a blue screen like that can only be caused by a driver problem, not by a user application like MSYS/MinGW. Is this problem repeatable? If you have any anti-virus software running, you might try disabling it to see if that is causing the problem. Does Windows give you any indication of which driver caused the fault? If not, you might try debugging the configure script to find which line is causing the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=102435&aid=1044081&group_id=2435 |