http://cygwin.com/lists.html#see-above
On Thu, Jan 17, 2002 at 12:42:35PM +0100, Dominik J?nicke wrote:
>
>gdb is hanging on NT with service pack5
>
>following steps was made:
>
>1. create a simple hello word program and compile it with debug option
>a.c
>#
>#include
>main()
>
gdb is hanging on NT with service pack5
following steps was made:
1. create a simple hello word program and compile it with debug option
a.c
#
#include
main()
{
printf("Hello World\n");
}
#
2. start the debugger
$ gdb a.exe
3. start execution with the run-b
I went and got WinXP today, installed the latest Cygwin and this
problem is gone. I presume that Win2K doesn't have this problem either,
but I'm happier now that I can debug in XP.
-tim
On Sunday, January 13, 2002, at 12:44 PM, Christopher Faylor wrote:
> On Sun, Jan 13, 2002 at 12:41
On Sunday, January 13, 2002, at 11:34 AM, Randall R Schulz wrote:
> If you're debugging a program written in a native language such as C or
> C++ (as opposed to a interpreted, protected language such as Java),
> then an "OS" without a strong memory protection model is hardly an
> advisable en
On Sun, Jan 13, 2002 at 12:41:27PM -0800, Timothy J. Wood wrote:
>
>On Sunday, January 13, 2002, at 11:29 AM, Christopher Faylor wrote:
>>It's a known problem in WinME. If gdb crashes for some reason while it
>>is debugging a program, then eventually Windows 9x, Windows ME, and, I
>>believe, Win
On Sunday, January 13, 2002, at 11:29 AM, Christopher Faylor wrote:
> It's a known problem in WinME. If gdb crashes for some reason while it
> is debugging a program, then eventually Windows 9x, Windows ME, and, I
> believe, Windows NT 4.0, will all hang.
So, Win2K should not have this prob
Tim,
If you're debugging a program written in a native language such as C or C++
(as opposed to a interpreted, protected language such as Java), then an
"OS" without a strong memory protection model is hardly an advisable
environment in which to do so. Your life will be full of pain if you try
On Sun, Jan 13, 2002 at 11:21:49AM -0800, Timothy J. Wood wrote:
>
>
> gdb typically runs fairly well for me, but in some cases where my
>program crashes, gdb prints out the fact that my program crashed and
>prints the name of some random function I've never heard of (I can get
>the name if it
gdb typically runs fairly well for me, but in some cases where my
program crashes, gdb prints out the fact that my program crashed and
prints the name of some random function I've never heard of (I can get
the name if it would help). gdb then appears to hang my machine.
Killing it via c
9 matches
Mail list logo
