On 20/03/2016 09:05, Ivan Pozdeev wrote:
gdb
---
I managed to debug the gdb session with VisualGDB (trial).
It turns out, the root cause is that the /bin/sh executable is x64, but
the core file `sh.exe.core' - of the same executable - has i386 format!
(objdump: <...>sh.exe.core: file format e
20.03.2016 15:47, Marco Atzeri пишет:
On 20/03/2016 10:05, Ivan Pozdeev wrote:
bash
I'm being plagued by these crashes for about half a month now.
Specifically, it cannot run any `configure' script.
The crashes appear to happen in child bash/sh processes launched while
processing backtick
On 20/03/2016 10:05, Ivan Pozdeev wrote:
bash
I'm being plagued by these crashes for about half a month now.
Specifically, it cannot run any `configure' script.
The crashes appear to happen in child bash/sh processes launched while
processing backticks. Other times, commands with stream redi
bash
I'm being plagued by these crashes for about half a month now.
Specifically, it cannot run any `configure' script.
The crashes appear to happen in child bash/sh processes launched while
processing backticks. Other times, commands with stream redirection fail
silently or produce nothing
On 03/13/2015 05:49 AM, Corinna Vinschen wrote:
On Mar 12 15:44, Gene Smith wrote:
I just updated cygwin and installed gdb. When I run it with no parameters it
crashes and prints:
:
/home/corinna/src/gdb/gdb-7.8/gdb-7.8.1.i686/src/gdb-7.8/gdb/common/common-utils.c:149
internal-error: xsprintf:
On Mar 12 15:44, Gene Smith wrote:
> I just updated cygwin and installed gdb. When I run it with no parameters it
> crashes and prints:
>
> :
> /home/corinna/src/gdb/gdb-7.8/gdb-7.8.1.i686/src/gdb-7.8/gdb/common/common-utils.c:149
> internal-error: xsprintf: Assertion `ret < size' failed.
> :
>
>
I just updated cygwin and installed gdb. When I run it with no
parameters it crashes and prints:
:
/home/corinna/src/gdb/gdb-7.8/gdb-7.8.1.i686/src/gdb-7.8/gdb/common/common-utils.c:149
internal-error: xsprintf: Assertion `ret < size' failed.
:
This is after downgrading to 7.8.1 but the lates
Dave Korn a écrit :
[...]
Is maybe one of you using gcc-3 with stabs debug and the other using gcc-4
with dwarf-2 debug?
I also forgot to ask, 1.5 or 1.7?
I use gcc 3 and gdb 6.8.0
it is the version 1.5 of setup (and I compile it with the gcc 3.4.4)
$ gcc --version
gcc (GCC) 3.4.4
Dave Korn wrote:
> Christopher Faylor wrote:
>> On Fri, Mar 13, 2009 at 09:59:44AM +0100, ludo wrote:
>>> /netrel/src/gdb-6.8-2/gdb/breakpoint.c:5082: internal-error:
>>> expand_line_sal_maybe: Assertion `found' failed.
>>> A problem internal to GDB has been detected,
>>> further debugging may pr
Christopher Faylor wrote:
> On Fri, Mar 13, 2009 at 09:59:44AM +0100, ludo wrote:
>> $ gdb ./setup.exe
>> (gdb) start
>> /netrel/src/gdb-6.8-2/gdb/breakpoint.c:5082: internal-error:
>> expand_line_sal_maybe: Assertion `found' failed.
>> A problem internal to GDB has been detected,
>> further deb
On Fri, Mar 13, 2009 at 09:59:44AM +0100, ludo wrote:
> Hi,
>
> I try to debug setup.exe but gdb crashes when I "start" the program
>
> * I get source of setup from CVS (sources.redhat.com:/cvs/cygwin-apps) and
> I build it with
>./doconfigure && make
Hi,
I try to debug setup.exe but gdb crashes when I "start" the program
* I get source of setup from CVS (sources.redhat.com:/cvs/cygwin-apps)
and I build it with
./doconfigure && make && make install
* I try to start a debugging session :
$ gdb ./setup.exe
On Mon, 14 Jul 2003, Christopher Faylor wrote:
> From: Christopher Faylor <[EMAIL PROTECTED]>
...snip...
> Just type "insight" to get insight.
>
> cgf
Ah, what that it were all so easy in life. -shrug-
Thanks for the perspective.
RT
--
Richard Troy, Chief Scientist
Science Tools Co
On Mon, Jul 14, 2003 at 07:16:47PM -0500, David A. Ferguson wrote:
>cygwin GDB crashes on single step
The version of gdb that is released with cygwin works fine with single
step. Just type "insight" to get insight.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-s
cygwin GDB crashes on single step
I am trying to get Insight operational on cygwin. After building every
thing I was attempting to debug a simple program. I can start the
debugger and run to a break point. It is when I attempt to single step
that gdb faults.
$ gdb a.exe
GNU gdb 2003
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
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
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, Windo
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
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
P? Is this a known
>problem in gdb?
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.
If gdb hangs it can get in the same state.
If you kill gdb from the
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
24 matches
Mail list logo
