From: Saeteurn S. <San...@gr...> - 2010-09-10 23:30:42
|
Howdy, I am trying to debug my program with MinGW GDB version 7.1 and I keep getting this error. After this error appears, the debug session hangs and pretty much dies. What does this error mean? It seems to happen spontaneously. NOTE: Please keep CC to my other e-mail account. I am using my work account, and the weekend is approaching. I would like to be able to follow up on this at home. Thankies ^^ -San Saeteurn ________________________________ San Saeteurn Software Engineer, Switching and Routing Solutions Engineering Grass Valley, Inc. Tel: (1) 530 478 3571 Fax: (1) 530 478 4020 Cell: (1) 530 370 7294 E-mail: san...@gr... <mailto:san...@gr...> Mail: Grass Valley 400 Providence Mine Road Nevada City, CA, 95959 USA |
From: Tatsh <dd...@gm...> - 2010-09-11 04:53:59
|
There are no real file descriptors on Windows. And there certainly isn't file descriptor 0 available for you to access. It might help to show some code. Saeteurn San wrote: > Howdy, > > > > I am trying to debug my program with MinGW GDB version 7.1 and I keep > getting this error. > > After this error appears, the debug session hangs and pretty much dies. > > > What does this error mean? It seems to happen spontaneously. > > > > NOTE: Please keep CC to my other e-mail account. I am using my work > account, and the weekend is approaching. > > I would like to be able to follow up on this at home. > > > > Thankies ^^ > > -San Saeteurn > > ________________________________ > > San Saeteurn > > Software Engineer, Switching and Routing Solutions Engineering > > Grass Valley, Inc. > > Tel: (1) 530 478 3571 > > Fax: (1) 530 478 4020 > > Cell: (1) 530 370 7294 > > E-mail: san...@gr... > <mailto:san...@gr...> > > Mail: > > Grass Valley > > 400 Providence Mine Road > > Nevada City, CA, 95959 > > USA -- Tatsh www.tatsh.net dd...@gm... |
From: Saeteurn S. <San...@gr...> - 2010-09-12 00:40:38
|
Howdy, I am working to port a massive 3+ million line system. I don't know how it works and there are many threads running. I don't really know what code to post lol... Do you have any ideas on what can cause something like this to happen so I can search for an appropriate part of the system that might be causing it and post segments from it? Googling this topic, it is said that this happens, on Linux, when someone attempts to pipe to gdb stdin. I know for a fact that we are not doing any piping to stdin. Not sure about stdout, we might be piping that to something, I'll have to ask one of the leads. Thankies ^^ -San Saeteurn ________________________________ San Saeteurn Software Engineer, Switching and Routing Solutions Engineering Grass Valley, Inc. Tel: (1) 530 478 3571 Fax: (1) 530 478 4020 Cell: (1) 530 370 7294 E-mail: san...@gr... Mail: Grass Valley 400 Providence Mine Road Nevada City, CA, 95959 USA -----Original Message----- From: Tatsh [mailto:dd...@gm...] Sent: Friday, September 10, 2010 9:54 PM To: MinGW Users List Cc: ssa...@gm... Subject: Re: [Mingw-users] Exception condition detected on fd 0 errordetected on stdin There are no real file descriptors on Windows. And there certainly isn't file descriptor 0 available for you to access. It might help to show some code. Saeteurn San wrote: > Howdy, > > > > I am trying to debug my program with MinGW GDB version 7.1 and I keep > getting this error. > > After this error appears, the debug session hangs and pretty much dies. > > > What does this error mean? It seems to happen spontaneously. > > > > NOTE: Please keep CC to my other e-mail account. I am using my work > account, and the weekend is approaching. > > I would like to be able to follow up on this at home. > > > > Thankies ^^ > > -San Saeteurn > > ________________________________ > > San Saeteurn > > Software Engineer, Switching and Routing Solutions Engineering > > Grass Valley, Inc. > > Tel: (1) 530 478 3571 > > Fax: (1) 530 478 4020 > > Cell: (1) 530 370 7294 > > E-mail: san...@gr... > <mailto:san...@gr...> > > Mail: > > Grass Valley > > 400 Providence Mine Road > > Nevada City, CA, 95959 > > USA -- Tatsh www.tatsh.net dd...@gm... ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ MinGW-users mailing list Min...@li... This list observes the Etiquette found at http://www.mingw.org/Mailing_Lists. We ask that you be polite and do the same. Disregard for the list etiquette may cause your account to be moderated. _______________________________________________ You may change your MinGW Account Options or unsubscribe at: https://lists.sourceforge.net/lists/listinfo/mingw-users |
From: Greg C. <gch...@sb...> - 2010-09-12 01:23:19
|
On 2010-09-12 00:40Z, Saeteurn San wrote: > > Googling this topic, it is said that this happens, on Linux, > when someone attempts to pipe to gdb stdin. I know for a fact > that we are not doing any piping to stdin. "Exception condition detected on fd 0" seems to be an internal diagnostic from gdb. For example, here on the gdb list: http://www.sourceware.org/ml/gdb/2007-04/msg00083.html is a MinGW case where an identical message arose when input was redirected into gdb with "cat cmds | gdb". How are you invoking gdb? Can you invoke it in a simpler way without receiving this message? You're using gdb-7.1; have you tried the latest version? http://sourceforge.net/projects/mingw/files_beta/MinGW/BaseSystem/GDB/GDB-7.2/ |
From: Saeteurn S. <San...@gr...> - 2010-09-13 20:38:49
Attachments:
main.cpp
|
Howdy List, I have found what causes this Exception! After some painful tracing through all the running threads I have traced the culprit to this situation: If your program is blocked on stdin read, i.e. using std::cin or gets, and the program gets interrupted so that gdb takes over you will get this error! I have attached a simple program that will do this. Basically, it contains two threads, the main thread spawns a new thread then blocks on stdin. The new thread sleeps for a seconds than causes a segmentation fault crash. GDB takes over, but stdin is still being held by the program, so gdb cannot use it! Hence the exception! Thankies ^^ -San Saeteurn ________________________________ San Saeteurn Software Engineer, Switching and Routing Solutions Engineering Grass Valley, Inc. Tel: (1) 530 478 3571 Fax: (1) 530 478 4020 Cell: (1) 530 370 7294 E-mail: san...@gr... Mail: Grass Valley 400 Providence Mine Road Nevada City, CA, 95959 USA -----Original Message----- From: Greg Chicares [mailto:gch...@sb...] Sent: Saturday, September 11, 2010 6:23 PM To: MinGW Users List Cc: Saeteurn San; ssa...@gm... Subject: Re: [Mingw-users] Exception condition detected on fd 0 errordetected on stdin On 2010-09-12 00:40Z, Saeteurn San wrote: > > Googling this topic, it is said that this happens, on Linux, > when someone attempts to pipe to gdb stdin. I know for a fact > that we are not doing any piping to stdin. "Exception condition detected on fd 0" seems to be an internal diagnostic from gdb. For example, here on the gdb list: http://www.sourceware.org/ml/gdb/2007-04/msg00083.html is a MinGW case where an identical message arose when input was redirected into gdb with "cat cmds | gdb". How are you invoking gdb? Can you invoke it in a simpler way without receiving this message? You're using gdb-7.1; have you tried the latest version? http://sourceforge.net/projects/mingw/files_beta/MinGW/BaseSystem/GDB/GDB-7.2/ |
From: Saeteurn S. <San...@gr...> - 2010-09-13 22:50:02
|
Also note that this issue doesn't happen with the Linux GDB. Seems to either be a bug in MinGW port or a difference with windows in handling stdin. Thankies ^^ -San Saeteurn ________________________________ San Saeteurn Software Engineer, Switching and Routing Solutions Engineering Grass Valley, Inc. Tel: (1) 530 478 3571 Fax: (1) 530 478 4020 Cell: (1) 530 370 7294 E-mail: san...@gr... Mail: Grass Valley 400 Providence Mine Road Nevada City, CA, 95959 USA -----Original Message----- From: Saeteurn San [mailto:San...@gr...] Sent: Monday, September 13, 2010 1:38 PM To: MinGW Users List Subject: Re: [Mingw-users] Exception condition detected on fd0 errordetected on stdin Howdy List, I have found what causes this Exception! After some painful tracing through all the running threads I have traced the culprit to this situation: If your program is blocked on stdin read, i.e. using std::cin or gets, and the program gets interrupted so that gdb takes over you will get this error! I have attached a simple program that will do this. Basically, it contains two threads, the main thread spawns a new thread then blocks on stdin. The new thread sleeps for a seconds than causes a segmentation fault crash. GDB takes over, but stdin is still being held by the program, so gdb cannot use it! Hence the exception! Thankies ^^ -San Saeteurn ________________________________ San Saeteurn Software Engineer, Switching and Routing Solutions Engineering Grass Valley, Inc. Tel: (1) 530 478 3571 Fax: (1) 530 478 4020 Cell: (1) 530 370 7294 E-mail: san...@gr... Mail: Grass Valley 400 Providence Mine Road Nevada City, CA, 95959 USA -----Original Message----- From: Greg Chicares [mailto:gch...@sb...] Sent: Saturday, September 11, 2010 6:23 PM To: MinGW Users List Cc: Saeteurn San; ssa...@gm... Subject: Re: [Mingw-users] Exception condition detected on fd 0 errordetected on stdin On 2010-09-12 00:40Z, Saeteurn San wrote: > > Googling this topic, it is said that this happens, on Linux, when > someone attempts to pipe to gdb stdin. I know for a fact that we are > not doing any piping to stdin. "Exception condition detected on fd 0" seems to be an internal diagnostic from gdb. For example, here on the gdb list: http://www.sourceware.org/ml/gdb/2007-04/msg00083.html is a MinGW case where an identical message arose when input was redirected into gdb with "cat cmds | gdb". How are you invoking gdb? Can you invoke it in a simpler way without receiving this message? You're using gdb-7.1; have you tried the latest version? http://sourceforge.net/projects/mingw/files_beta/MinGW/BaseSystem/GDB/GDB-7.2/ |
From: Saeteurn S. <San...@gr...> - 2010-09-16 16:18:32
|
Well, it seems that no one is responding to this thread... This seems like a major bug in GDB, you can't trace if you have a thread waiting on stdin. This happens in the latest version, 7.2 as well. Thankies ^^ -San Saeteurn ________________________________ San Saeteurn Software Engineer, Switching and Routing Solutions Engineering Grass Valley, Inc. Tel: (1) 530 478 3571 Fax: (1) 530 478 4020 Cell: (1) 530 370 7294 E-mail: san...@gr... Mail: Grass Valley 400 Providence Mine Road Nevada City, CA, 95959 USA -----Original Message----- From: Saeteurn San [mailto:San...@gr...] Sent: Monday, September 13, 2010 3:50 PM To: MinGW Users List Subject: Re: [Mingw-users] Exception condition detected on fd0 errordetectedon stdin Also note that this issue doesn't happen with the Linux GDB. Seems to either be a bug in MinGW port or a difference with windows in handling stdin. Thankies ^^ -San Saeteurn ________________________________ San Saeteurn Software Engineer, Switching and Routing Solutions Engineering Grass Valley, Inc. Tel: (1) 530 478 3571 Fax: (1) 530 478 4020 Cell: (1) 530 370 7294 E-mail: san...@gr... Mail: Grass Valley 400 Providence Mine Road Nevada City, CA, 95959 USA -----Original Message----- From: Saeteurn San [mailto:San...@gr...] Sent: Monday, September 13, 2010 1:38 PM To: MinGW Users List Subject: Re: [Mingw-users] Exception condition detected on fd0 errordetected on stdin Howdy List, I have found what causes this Exception! After some painful tracing through all the running threads I have traced the culprit to this situation: If your program is blocked on stdin read, i.e. using std::cin or gets, and the program gets interrupted so that gdb takes over you will get this error! I have attached a simple program that will do this. Basically, it contains two threads, the main thread spawns a new thread then blocks on stdin. The new thread sleeps for a seconds than causes a segmentation fault crash. GDB takes over, but stdin is still being held by the program, so gdb cannot use it! Hence the exception! Thankies ^^ -San Saeteurn ________________________________ San Saeteurn Software Engineer, Switching and Routing Solutions Engineering Grass Valley, Inc. Tel: (1) 530 478 3571 Fax: (1) 530 478 4020 Cell: (1) 530 370 7294 E-mail: san...@gr... Mail: Grass Valley 400 Providence Mine Road Nevada City, CA, 95959 USA -----Original Message----- From: Greg Chicares [mailto:gch...@sb...] Sent: Saturday, September 11, 2010 6:23 PM To: MinGW Users List Cc: Saeteurn San; ssa...@gm... Subject: Re: [Mingw-users] Exception condition detected on fd 0 errordetected on stdin On 2010-09-12 00:40Z, Saeteurn San wrote: > > Googling this topic, it is said that this happens, on Linux, when > someone attempts to pipe to gdb stdin. I know for a fact that we are > not doing any piping to stdin. "Exception condition detected on fd 0" seems to be an internal diagnostic from gdb. For example, here on the gdb list: http://www.sourceware.org/ml/gdb/2007-04/msg00083.html is a MinGW case where an identical message arose when input was redirected into gdb with "cat cmds | gdb". How are you invoking gdb? Can you invoke it in a simpler way without receiving this message? You're using gdb-7.1; have you tried the latest version? http://sourceforge.net/projects/mingw/files_beta/MinGW/BaseSystem/GDB/GDB-7.2/ ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ MinGW-users mailing list Min...@li... This list observes the Etiquette found at http://www.mingw.org/Mailing_Lists. We ask that you be polite and do the same. Disregard for the list etiquette may cause your account to be moderated. _______________________________________________ You may change your MinGW Account Options or unsubscribe at: https://lists.sourceforge.net/lists/listinfo/mingw-users |
From: Jasper H. <jas...@gm...> - 2010-09-17 02:17:30
|
Saeteurn San wrote: > Well, it seems that no one is responding to this thread... Keep in mind nobody is getting paid here - all help you get is voluntary. > This seems like a major bug in GDB, Perhaps you have heard of the principle of "debugging the debugger", I can assure you it's not a pretty sight. Anyway, for such a major bug you are much better off filing a bug report than posting here. Jasper |