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
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
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
3, 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 W
4 matches
Mail list logo
