Re: gdb problem

On 04/05/2012 1:19 PM, Ken Brown wrote: On 5/3/2012 11:10 PM, Christopher Faylor wrote: On Thu, May 03, 2012 at 04:05:04PM -0400, Ken Brown wrote: On 10/23/2011 5:47 PM, Ken Brown wrote: On 10/23/2011 3:04 PM, Christopher Faylor wrote: On Sat, Oct 22, 2011 at 04:37:55PM -0400, Ken Brown wrote

Re: gdb problem

On 5/3/2012 11:10 PM, Christopher Faylor wrote: On Thu, May 03, 2012 at 04:05:04PM -0400, Ken Brown wrote: On 10/23/2011 5:47 PM, Ken Brown wrote: On 10/23/2011 3:04 PM, Christopher Faylor wrote: On Sat, Oct 22, 2011 at 04:37:55PM -0400, Ken Brown wrote: The attached testcase illustrates a pr

Re: gdb problem

On Thu, May 03, 2012 at 04:05:04PM -0400, Ken Brown wrote: >On 10/23/2011 5:47 PM, Ken Brown wrote: >> On 10/23/2011 3:04 PM, Christopher Faylor wrote: >>> On Sat, Oct 22, 2011 at 04:37:55PM -0400, Ken Brown wrote: The attached testcase illustrates a problem with `gdb -i=mi'. I've tested

Re: gdb problem

On 10/23/2011 5:47 PM, Ken Brown wrote: On 10/23/2011 3:04 PM, Christopher Faylor wrote: On Sat, Oct 22, 2011 at 04:37:55PM -0400, Ken Brown wrote: The attached testcase illustrates a problem with `gdb -i=mi'. I've tested both gdb 7.3.50-1 and 7.3.50-2, with cygwin 1.7.9 as well as with several

Re: gdb problem

On 10/23/2011 3:04 PM, Christopher Faylor wrote: On Sat, Oct 22, 2011 at 04:37:55PM -0400, Ken Brown wrote: The attached testcase illustrates a problem with `gdb -i=mi'. I've tested both gdb 7.3.50-1 and 7.3.50-2, with cygwin 1.7.9 as well as with several recent snapshots (including 2011-10-22)

Re: gdb problem

On Sat, Oct 22, 2011 at 04:37:55PM -0400, Ken Brown wrote: >The attached testcase illustrates a problem with `gdb -i=mi'. I've >tested both gdb 7.3.50-1 and 7.3.50-2, with cygwin 1.7.9 as well as with >several recent snapshots (including 2011-10-22). > >Under some circumstances, if gdb -i=mi is

Re: gdb problem

Difference with Linux might be matter of timing. (Or, might gdb version). The problem is that gdb calls poll() while it has (all) data already in libc buffers. It also calls fileno() and isatty() arround that time. (Also {m,c,re}alloc, free, pthread_sigmask, vsprints) Gdb first calls poll() wit

RE: GDB problem (under cygwin)

On 08 March 2007 18:50, Raymond Miller wrote: > omg, I would never have imagined that that were the problem. You're not the only one, there is really no need at all for a webcam software to inject itself into every process in the system! It is a *very* peculiar piece of design and a very bad c

Re: GDB problem (under cygwin)

omg, I would never have imagined that that were the problem. I thanks you very much, I was crazy already. Not it works. Thanks! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/

RE: GDB problem (under cygwin)

On 08 March 2007 18:12, Raymond Miller wrote: > Yes, I have installed in this pc (laptop) the Logitech webcam software and > this is not installed in the desktop pc (I don't have any webcam on that > pc), but could be it the cause of the segmentation fault? Yes! Disable "Logitech process moni

Re: GDB problem (under cygwin)

Raymond Miller wrote: Yes, I have installed in this pc (laptop) the Logitech webcam software and this is not installed in the desktop pc (I don't have any webcam on that pc), but could be it the cause of the segmentation fault? I wouldn't discount it until you've uninstalled it and reproduced

Re: GDB problem (under cygwin)

int main () { printf("hello"); return 0; } Ok, I compiled the code.c with the cygwin gcc C:\Documents and Settings\Rafa\Desktop>gcc code.c -g -o program.exe I ran the cygwin gdb C:\Documents and Settings\Rafa\Desktop>gdb program.exe GNU gdb 6.5.50.20060706-cvs (cygwin-special) Copyright (C) 200

RE: GDB problem (under cygwin)

On 08 March 2007 17:33, Raymond Miller wrote: > No, I don't think that my program has a bug. > Ok, this is the code of my program (C): > > #include > > int main () > { > printf("hello"); > return 0; > } Ok, just to be certain I checked it myself, (I have the same gcc/gdb versions), and it wo

Re: GDB problem (under cygwin)

Raymond Miller wrote: > No, I don't think that my program has a bug. > Ok, this is the code of my program (C): > > #include > > int main () > { > printf("hello"); > return 0; > } > > Another code with the same problem (Segmentation fault) > > int main () > { > return 0; > } > > And I could f

Re: GDB problem (under cygwin)

No, I don't think that my program has a bug. Ok, this is the code of my program (C): #include int main () { printf("hello"); return 0; } Another code with the same problem (Segmentation fault) int main () { return 0; } And I could follow writting codes because all have the same problem. >

RE: GDB problem (under cygwin)

On 08 March 2007 14:43, Raymond Miller wrote: > Finally I found what is the problem. No, I don't think you have. You haven't even clearly identified a problem. You say that the problem is that gdb reports a SIGSEGV in thread 2 when you compiled with cygwin gcc, but for all anyone knows tha

Re: GDB problem (under cygwin)

Finally I found what is the problem. The problem wasn't the Eclipse IDE because I couldn't debug either with the gdb.exe ( in command-line) and in addition I installed Cygwin and Eclipse IDE in the desktop PC (AMD 64 3400+ with Windows XP Home and Ubuntu) and I could compile and debug without an

Re: GDB problem (under cygwin)

Raymond Miller wrote: Can someone say me what am I doing wrong? With mingw I can debug without problem (doing the make with mingw32-make). Then what's the problem?. Not with the information provided at least. See: Problem reports: http://cygwin.com/problems.html I'm not sure allot o

Re: GDB problem (under cygwin)

Can someone say me what am I doing wrong? With mingw I can debug without problem (doing the make with mingw32-make). Then what's the problem?. Cya -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation:

Re: GDB problem (under cygwin)

. Redirecting to the list. On Tue, 6 Mar 2007, Kabal wrote: > Hi, I saw some messages written by you and I would want know if you could > help me with a problem. > I have installed cygwin (devel package) and I have added the Environment > variable in the path

Re: gdb problem - cygwin-1.5.19-4

Thanks, I totally forgot to look in the mailing list archive. Yann COLLETTE -- Disclaimer Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus.

Re: gdb problem - cygwin-1.5.19-4

COLLETTE Yann wrote: > Program received signal SIGSEGV, Segmentation fault. > 0x610ae938 in pthread_key_create () from /usr/bin/cygwin1.dll This is a meaningless and benign message. Just type "continue". Search the mailing list archives for details. Brian -- Unsubscribe info: http://cygw

Re: gdb problem

On Tue, Jan 27, 2004 at 02:38:28PM +0100, RS wrote: >>Don't use CYGWIN=tty when debugging. It confuses the debugee. > >First of all thank you, it really helps when I start a shell using >"cygwin\cygwin.bat". Ok. So, if you want to do this, then you will observe the behavior that you mentioned.

RE: gdb problem

> Don't use CYGWIN=tty when debugging. It confuses the debugee. > cgf First of all thank you, it really helps when I start a shell using "cygwin\cygwin.bat". But I do not understand why it helps, because gdb is a unix program and I thought that problems with tty option may occur with Windows prog

Re: gdb problem

On Mon, Jan 26, 2004 at 08:23:00PM +0100, RS wrote: >Using gdb under cygwin I had a problem that can be demonstrated with >following little program: >[snip] >Under Cygwin (Win98 and Win2k) text written to stdout is printed only >after finishing the >Thank you for any hint, Don't use CYGWIN=tty whe