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
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
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
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 both gdb
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
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
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 started and given several
input lines at once, it only prints
break cygwin_select
--
View this message in context:
http://old.nabble.com/gdb-problem-tp32702884p32703871.html
Sent from the Cygwin list mailing list archive at Nabble.com.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation
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
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
No, I don't think that my program has a bug.
Ok, this is the code of my program (C):
#include stdio.h
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.
Raymond Miller wrote:
No, I don't think that my program has a bug.
Ok, this is the code of my program (C):
#include stdio.h
int main ()
{
printf(hello);
return 0;
}
Another code with the same problem (Segmentation fault)
int main ()
{
return 0;
}
And I could follow
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 stdio.h
int main ()
{
printf(hello);
return 0;
}
Ok, just to be certain I checked it myself, (I have the same gcc/gdb
versions), and it worked
int main ()
{
printf(hello);
return 0;
}
Ok, I compiled the code.c with the cygwin gcc
C:\Documents and Settings\Rafa\Desktopgcc code.c -g -o program.exe
I ran the cygwin gdb
C:\Documents and Settings\Rafa\Desktopgdb program.exe
GNU gdb 6.5.50.20060706-cvs (cygwin-special)
Copyright (C) 2006
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
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 monitor
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:
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
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:
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
to NTFS-)
But I cannot get the answer for this gdb-problem, thanks.
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!)
|,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
Hello,
I've a problem with gdb. The message displayed by gdb is the following:
(gdb) run
Starting program: /cygdrive/g/MAPAO/Optim_2/Main/Reg/OptimizeReg.exe
Program received signal SIGSEGV, Segmentation fault.
0x610ae938 in pthread_key_create () from /usr/bin/cygwin1.dll
(gdb) where
#0
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:
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
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.
But I
Using gdb under cygwin I had a problem that can be demonstrated with
following
little program:
==
#include stdio.h
int main()
{
char str[100];
printf(Hello !\n);
scanf(%s, str);
printf(str: %s\n, str);
scanf(%s, str);
printf(str: %s\n, str);
return
27 matches
Mail list logo
