Re: new gdb interface
At 09:07 2002-10-17, you wrote: On Thu, Oct 17, 2002 at 04:10:35AM -0400, CBFalconer wrote: Thomas Mellman wrote: Thank you, that helped. Nevertheless, let me re-iterate my plea: particularly in the CYGWIN world, fancy do-dads should be optional, rather than standard Unix command line behaviour (IMHO) being optional. Amen. Hallelujah! Praise the Lord! Nothing invented since 1980 is even remotely an improvement on what came before. Progress -- Bah! RRS -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: new gdb interface
On Thu, Oct 17, 2002 at 04:10:35AM -0400, CBFalconer wrote: Thomas Mellman wrote: Thank you, that helped. Nevertheless, let me re-iterate my plea: particularly in the CYGWIN world, fancy do-dads should be optional, rather than standard Unix command line behaviour (IMHO) being optional. Amen. Hallelujah! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
new gdb interface
I'm not sure if this is a cygwin issue, but... I just ran gdb for the first time on CYGWIN to debug a little program I'm writing All of a sudden up pops a graphics window. Now, I've used gdb for many years, enjoy it, and can operate it. I can't operate this graphical interface and don't want it. After 10 minutes of looking at the man page (written with the Microsoft familiar-you) and info stuff, I see no clear instructions how *not* to get the graphical interface. Everything seems to address the old, non-graphical interface (hence my suspicion that this is a CYGWIN issue ) In trying to kill it, I now have an unkillable, dead window on my screen. Can anybody tell me how to run real gdb? And can graphical interfaces please be optional, rather than the other way around? A graphical interface for a debugger is not a bad idea, and this one may be a good one (there are already good ones, like ddd, but that's besides the point), but when I want a graphical interface, I'll execute it. -- Thomas Mellman [EMAIL PROTECTED] Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: new gdb interface
try gdb --help Al -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Thomas Mellman Sent: 17 October 2002 08:02 To: [EMAIL PROTECTED] Subject: new gdb interface I'm not sure if this is a cygwin issue, but... I just ran gdb for the first time on CYGWIN to debug a little program I'm writing All of a sudden up pops a graphics window. Now, I've used gdb for many years, enjoy it, and can operate it. I can't operate this graphical interface and don't want it. After 10 minutes of looking at the man page (written with the Microsoft familiar-you) and info stuff, I see no clear instructions how *not* to get the graphical interface. Everything seems to address the old, non-graphical interface (hence my suspicion that this is a CYGWIN issue ) In trying to kill it, I now have an unkillable, dead window on my screen. Can anybody tell me how to run real gdb? And can graphical interfaces please be optional, rather than the other way around? A graphical interface for a debugger is not a bad idea, and this one may be a good one (there are already good ones, like ddd, but that's besides the point), but when I want a graphical interface, I'll execute it. -- Thomas Mellman [EMAIL PROTECTED] Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: new gdb interface
Hi! Thursday, 17 October, 2002 Thomas Mellman [EMAIL PROTECTED] wrote: TM I had to power down my box - neither kill(-9) on either the process under test, TM the debugger or the debugger window, nor even the task manager were able TM to kill the two processes, and even windows-shutdown hung. This is (probably) a bug in windows debugging interface. Similar hangs (when one tries to kill debugee or debugger, and then they both remains unkillable) are not gdb specific. They occur with any windows program which exercise debugging APIs. Egor.mailto:[EMAIL PROTECTED] ICQ 5165414 FidoNet 2:5020/496.19 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: new gdb interface
Thomas Mellman wrote: Thank you, that helped. Nevertheless, let me re-iterate my plea: particularly in the CYGWIN world, fancy do-dads should be optional, rather than standard Unix command line behaviour (IMHO) being optional. Amen. -- Chuck F ([EMAIL PROTECTED]) ([EMAIL PROTECTED]) Available for consulting/temporary embedded and systems. http://cbfalconer.home.att.net USE worldnet address! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Re: new gdb interface
egor duda [EMAIL PROTECTED] schrieb am 17.10.02 10:10:39: Hi! Thursday, 17 October, 2002 Thomas Mellman [EMAIL PROTECTED] wrote: TM I had to power down my box - neither kill(-9) on either the process under test, TM the debugger or the debugger window, nor even the task manager were able TM to kill the two processes, and even windows-shutdown hung. This is (probably) a bug in windows debugging interface. Similar hangs (when one tries to kill debugee or debugger, and then they both remains unkillable) are not gdb specific. They occur with any windows program which exercise debugging APIs. Ah. Good. Thank you. -- Thomas Mellman [EMAIL PROTECTED] Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: new gdb interface
Hi... Cygwin uses insight, the gnu gdb frontend (which when you got used to it, can help a lot) and which is included in newer gdb versions.It is *NOT* a cygwin extenstion. To start in traditional mode run gdb with the -nw option. Roland Thomas Mellman [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 17.10.2002 09:02 To: [EMAIL PROTECTED] cc: Subject: new gdb interface I'm not sure if this is a cygwin issue, but... I just ran gdb for the first time on CYGWIN to debug a little program I'm writing All of a sudden up pops a graphics window. Now, I've used gdb for many years, enjoy it, and can operate it. I can't operate this graphical interface and don't want it. After 10 minutes of looking at the man page (written with the Microsoft familiar-you) and info stuff, I see no clear instructions how *not* to get the graphical interface. Everything seems to address the old, non-graphical interface (hence my suspicion that this is a CYGWIN issue ) In trying to kill it, I now have an unkillable, dead window on my screen. Can anybody tell me how to run real gdb? And can graphical interfaces please be optional, rather than the other way around? A graphical interface for a debugger is not a bad idea, and this one may be a good one (there are already good ones, like ddd, but that's besides the point), but when I want a graphical interface, I'll execute it. -- Thomas Mellman [EMAIL PROTECTED] -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: new gdb interface
As mentioned, the behavior of gdb is driven by the developers of gdb and insight. You should address your questions and concerns in this area to the gdb list. Larry Original Message: - From: Thomas Mellman [EMAIL PROTECTED] Date: Thu, 17 Oct 2002 11:31:03 +0200 To: [EMAIL PROTECTED] Subject: Re: new gdb interface Regarding the default window-fied behaviour of GDB - is that POSIX? It certainly doesn't seem in the spirit of POSIX. -- Thomas Mellman [EMAIL PROTECTED] Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ mail2web - Check your email from the web at http://mail2web.com/ . -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
