Brian Dessent wrote:
Eric Lilja wrote:
Now I want to put a breakpoint somewhere and print some variables when
that breakpoint is hit. Can I do that in this scenario? If so, how do I
make gdb find emacs sources? Doing
$ break /cygdrive/c/full/path/to/source/file:1337 doesn't work (No
source file
Eric Lilja wrote:
> Now I want to put a breakpoint somewhere and print some variables when
> that breakpoint is hit. Can I do that in this scenario? If so, how do I
> make gdb find emacs sources? Doing
> $ break /cygdrive/c/full/path/to/source/file:1337 doesn't work (No
> source file named blah bl
I have a native windows program (compiled using cygwin's gcc acting in
mingw mode, with debugging information), can I debug it using cygwin's
gdb? It's emacs I'm talking about and I'm trying to provide the
developers information about a crash on windows vista. Doing this works
fine:
$ gdb emac
Well, I'm not sure about this course. I was actually more
inclined to suspect that there may be something odd with
our device than with cygwin. Towards this end I figured
I should be able to snoop the innards of the ftpd in order
to figure out who/what's going on. At this point I'm
suspecting t
On Tue, Oct 01, 2002 at 04:00:24PM -0400, Bruce P. Osler wrote:
>Can anybody perhaps throw a hint over the fence to me about how I might
>go about debugging this issue?
How about trying the latest cygwin snapshot at http://cygwin.com/snapshots/ ?
If it is a problem in cygwin it might be fixed the
I'm currently attempting to debug network boot (via ftp) of a
networking device for which I'm responsible. The devices ftp
client is based on a horribly antiquated vxworks kernel. The
cygwin I'm using has been recently updated and includes
inetutils release (1.3.2)
The issue isn't one of comple
6 matches
Mail list logo
