I compiled the latest gcc and gdb and it now works under cygwin.
The versions I'm using are:
D:\projects\Eclipse\CDT\HelloWorld2\Debug>gcc --version
gcc (GCC) 4.2.3
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warrant
A Monday 18 February 2008 03:55:45, Ray Hurst wrote:
> Di I need to actually take the source changes from this thread and apply
> them to my build?
> Or is there a patch file available?
That *is* a patch file. It's a text file with inline disposition, so you can
get at the exact file contents wi
A Sunday 17 February 2008 03:37:38, Christopher Faylor wrote:
> On Sun, Feb 17, 2008 at 03:19:02AM +, Pedro Alves wrote:
> >http://sourceware.org/ml/gdb-patches/2007-11/msg00567.html
>
> Was that patch applied? AFAICT from the ChangeLog's it wasn't.
>
> If not, have you pinged anyone about thi
Pedro Alves wrote:
A Friday 15 February 2008 23:21:45, Ray Hurst wrote:
Here is a run of a HellowWorld program (listed below in gdb).
Can someone tell me why the variables a, b, c are not the correct
values. I dumped the local stack and the variables are correct on the
stack.
I'm running Win
On Sun, Feb 17, 2008 at 03:19:02AM +, Pedro Alves wrote:
>A Friday 15 February 2008 23:21:45, Ray Hurst wrote:
>>Here is a run of a HellowWorld program (listed below in gdb).
>>
>>Can someone tell me why the variables a, b, c are not the correct
>>values. I dumped the local stack and the varia
A Friday 15 February 2008 23:21:45, Ray Hurst wrote:
> Here is a run of a HellowWorld program (listed below in gdb).
>
> Can someone tell me why the variables a, b, c are not the correct
> values. I dumped the local stack and the variables are correct on the
> stack.
>
> I'm running Windows XP und
Here is a run of a HellowWorld program (listed below in gdb).
Can someone tell me why the variables a, b, c are not the correct
values. I dumped the local stack and the variables are correct on the stack.
I'm running Windows XP under cygwin.
gcc 4.2.3
The gdb run is as follows:
GNU gdb 6.5.5
Ray Hurst wrote:
Marco Atzeri wrote:
--- Ray Hurst <[EMAIL PROTECTED]> ha scritto:
Works fine on my Windows XP Pro machine using the
same GDB and gcc
version 3.4.4. What gcc version do you have?
The stack trace would indicate that the crash is
occurring before it
gets to your main functio
Marco Atzeri wrote:
--- Ray Hurst <[EMAIL PROTECTED]> ha scritto:
Works fine on my Windows XP Pro machine using the
same GDB and gcc
version 3.4.4. What gcc version do you have?
The stack trace would indicate that the crash is
occurring before it
gets to your main function, since that code
--- Ray Hurst <[EMAIL PROTECTED]> ha scritto:
> > Works fine on my Windows XP Pro machine using the
> same GDB and gcc
> > version 3.4.4. What gcc version do you have?
> >
> > The stack trace would indicate that the crash is
> occurring before it
> > gets to your main function, since that code
Jim Marshall wrote:
Ray Hurst wrote:
I'm running under Windows XP and Cygwin.
I ran GDB on a simple C program and captured the output (below).
I have a few questions:
Why can I run the program several times with no errors but as soon as
I set a breakpoint at main it gets a SIGSEGV fault?
Wh
Ray Hurst wrote:
I'm running under Windows XP and Cygwin.
I ran GDB on a simple C program and captured the output (below).
I have a few questions:
Why can I run the program several times with no errors but as soon as I
set a breakpoint at main it gets a SIGSEGV fault?
Why does the backtrace
I'm running under Windows XP and Cygwin.
I ran GDB on a simple C program and captured the output (below).
I have a few questions:
Why can I run the program several times with no errors but as soon as I
set a breakpoint at main it gets a SIGSEGV fault?
Why does the backtrace show only addresse
13 matches
Mail list logo
