cgdb-devel

[Cgdb-devel] compile for cygwin

[Armin D. <di...@no...>]

Hi,

i'm tying to compile for cygwin, the compile runs fine but the resulting 
cgdb.exe will core dump:

$ gdb-old --args ./cgdb -d /bin/gdb-old.exe
GNU gdb 2003-03-03-cvs (cygwin-special)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-cygwin"...
(gdb) r
Starting program: /usr/src/cgdb-0.2.3/src/cgdb.exe -d /bin/gdb-old.exe

Program received signal SIGSEGV, Segmentation fault.
0x610c540a in wmemset () from /usr/bin/cygwin1.dll
(gdb) bt
#0  0x610c540a in wmemset () from /usr/bin/cygwin1.dll
#1  0x610b3409 in fputs () from /usr/bin/cygwin1.dll
#2  0x0040dfed in io_debug_write_fmt (fmt=0x4100dc "[%s]") at io.c:74
#3  0x00410434 in tgdb_init_forkAndExecPty (debugger=0x22ff01 
"/bin/gdb-old.exe", argc=0, argv=0x100
50d2c, slavename=0x41a9c0 "", masterfd=0x414718, need_nl_mapping=0) at 
tgdb_init.c:95
#4  0x0040b120 in tgdb_init (debugger=0x22ff01 "/bin/gdb-old.exe", 
argc=0, argv=0x10050d2c, gdb=0x41
41f0, child=0x4141f4) at tgdb.c:95
#5  0x00402d81 in start_gdb (argc=0, argv=0x10050d2c) at cgdb.c:226
#6  0x0040383b in main (argc=0, argv=0x10050d2c) at cgdb.c:539
(gdb)

This happens with the 0.2.3 version. I also tried the cvs version, it 
will not core dump but will print nonsense in the upper half of the 
screen and hangs after that.

Re: [Cgdb-devel] compile for cygwin

[Peter K. <pe...@ko...>]

The main developer is on vacation at the moment, although he might get a
chance to check his mail.  I know that in the past we had problems
running under cygwin because cgdb creates a pseudo-tty in order to talk
to gdb.  This should be removed in CVS, however the CVS version is a
little unstable at the moment. =20

- Peter

On Tue, Mar 18, 2003 at 01:56:14PM +0100, Armin Diehl wrote:
> Hi,
>=20
> i'm tying to compile for cygwin, the compile runs fine but the resulting=
=20
> cgdb.exe will core dump:
>=20
> $ gdb-old --args ./cgdb -d /bin/gdb-old.exe
> GNU gdb 2003-03-03-cvs (cygwin-special)
> Copyright 2003 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you =
are
> welcome to change it and/or distribute copies of it under certain=20
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for detail=
s.
> This GDB was configured as "i686-pc-cygwin"...
> (gdb) r
> Starting program: /usr/src/cgdb-0.2.3/src/cgdb.exe -d /bin/gdb-old.exe
>=20
> Program received signal SIGSEGV, Segmentation fault.
> 0x610c540a in wmemset () from /usr/bin/cygwin1.dll
> (gdb) bt
> #0  0x610c540a in wmemset () from /usr/bin/cygwin1.dll
> #1  0x610b3409 in fputs () from /usr/bin/cygwin1.dll
> #2  0x0040dfed in io_debug_write_fmt (fmt=3D0x4100dc "[%s]") at io.c:74
> #3  0x00410434 in tgdb_init_forkAndExecPty (debugger=3D0x22ff01=20
> "/bin/gdb-old.exe", argc=3D0, argv=3D0x100
> 50d2c, slavename=3D0x41a9c0 "", masterfd=3D0x414718, need_nl_mapping=3D0)=
 at=20
> tgdb_init.c:95
> #4  0x0040b120 in tgdb_init (debugger=3D0x22ff01 "/bin/gdb-old.exe",=20
> argc=3D0, argv=3D0x10050d2c, gdb=3D0x41
> 41f0, child=3D0x4141f4) at tgdb.c:95
> #5  0x00402d81 in start_gdb (argc=3D0, argv=3D0x10050d2c) at cgdb.c:226
> #6  0x0040383b in main (argc=3D0, argv=3D0x10050d2c) at cgdb.c:539
> (gdb)
>=20
> This happens with the 0.2.3 version. I also tried the cvs version, it=20
> will not core dump but will print nonsense in the upper half of the=20
> screen and hangs after that.

--=20
Peter D. Kovacs <pe...@ko...>

Re: [Cgdb-devel] compile for cygwin

[Bob R. <bob...@co...>]

On Tue, Mar 18, 2003 at 08:14:41AM -0500, Peter Kovacs wrote:
> The main developer is on vacation at the moment, although he might get a
> chance to check his mail.  I know that in the past we had problems
> running under cygwin because cgdb creates a pseudo-tty in order to talk
> to gdb.  This should be removed in CVS, however the CVS version is a
> little unstable at the moment. =20
>=20
> - Peter
>=20
> On Tue, Mar 18, 2003 at 01:56:14PM +0100, Armin Diehl wrote:
> > Hi,
> >=20
> > I'm tying to compile for cygwin, the compile runs fine but the resultin=
g=20
> > cgdb.exe will core dump:

hmmm, I have had bad luck trying to support cygwin. I find that I can
get cgdb to work find for win NT, 2000 and then I run it on XP and it
doesn't work ( just an example ). I am not sure why your configuration=20
is core dumping. I do use cgdb almost daily on cygwin at work on a
windows 2000 and windows NT box.

> >=20
> > $ gdb-old --args ./cgdb -d /bin/gdb-old.exe
> > GNU gdb 2003-03-03-cvs (cygwin-special)
> > Copyright 2003 Free Software Foundation, Inc.
> > GDB is free software, covered by the GNU General Public License, and yo=
u are
> > welcome to change it and/or distribute copies of it under certain=20
> > conditions.
> > Type "show copying" to see the conditions.
> > There is absolutely no warranty for GDB.  Type "show warranty" for deta=
ils.
> > This GDB was configured as "i686-pc-cygwin"...
> > (gdb) r
> > Starting program: /usr/src/cgdb-0.2.3/src/cgdb.exe -d /bin/gdb-old.exe
> >=20
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x610c540a in wmemset () from /usr/bin/cygwin1.dll
> > (gdb) bt
> > #0  0x610c540a in wmemset () from /usr/bin/cygwin1.dll
> > #1  0x610b3409 in fputs () from /usr/bin/cygwin1.dll
> > #2  0x0040dfed in io_debug_write_fmt (fmt=3D0x4100dc "[%s]") at io.c:74
> > #3  0x00410434 in tgdb_init_forkAndExecPty (debugger=3D0x22ff01=20
> > "/bin/gdb-old.exe", argc=3D0, argv=3D0x100
> > 50d2c, slavename=3D0x41a9c0 "", masterfd=3D0x414718, need_nl_mapping=3D=
0) at=20
> > tgdb_init.c:95
> > #4  0x0040b120 in tgdb_init (debugger=3D0x22ff01 "/bin/gdb-old.exe",=20
> > argc=3D0, argv=3D0x10050d2c, gdb=3D0x41
> > 41f0, child=3D0x4141f4) at tgdb.c:95
> > #5  0x00402d81 in start_gdb (argc=3D0, argv=3D0x10050d2c) at cgdb.c:226
> > #6  0x0040383b in main (argc=3D0, argv=3D0x10050d2c) at cgdb.c:539
> > (gdb)

I will try to reproduce this when I get back home with the latest update
of cygwin. Are you using a non-standard gdb? ( I noticed gdb-old.exe ).
One funny thing you might try is to name the debugger you are starting just
gdb.exe or gdb ( That may or may not be a bug on my part :) ).

What compiler are you using to compile cgdb?
What OS are you running?

> >=20
> > This happens with the 0.2.3 version. I also tried the cvs version, it=
=20
> > will not core dump but will print nonsense in the upper half of the=20
> > screen and hangs after that.

cgdb 0.2.3 is the most stable. However, the cgdb team has had trouble
changing cgdb because of its design. So, an effort to redesign several
core components is underway in cvs. Unfortunately it is not ready yet. I
hope to have it done by the end of the first week in April. After that,
we will be testing it. If all goes well, then cgdb 0.3.0 will be
released.

This is the best I can offer.

Thanks,
Bob Rossi

Re: [Cgdb-devel] compile for cygwin

[Armin D. <di...@no...>]

Bob,

> What compiler are you using to compile cgdb?
> What OS are you running?

The machine where i compiled and got the segfault was xp, cygwin was installed 
a few days ago.
Compiler is gcc version 3.2 20020927 (prerelease), this is the version that was 
included in the cygwin distribution.

and i forgot: in io.c it dumps core because dfd is null (fprintf(dfd, "%s", 
va_buf);) in io_debug_write

and gdb-old.exe is the original that was included in cygwin (GNU gdb 
2003-03-03-cvs (cygwin-special))

i also tryed a plain 5.3 and also renamed it to gdb.exe but no difference. (5.3 
works fine on linux)
It is not urgent for me because i can work on linux. (and there cgdb work fine)

Another short question: Is it possible to automate the :set sc ?

Thanks for your help !

Re: [Cgdb-devel] compile for cygwin

[Bob R. <bob...@co...>]

On Tue, Mar 18, 2003 at 11:16:39PM +0100, Armin Diehl wrote:
> Bob,
>=20
> >What compiler are you using to compile cgdb?
> >What OS are you running?
>=20
> The machine where i compiled and got the segfault was xp, cygwin was=20
> installed a few days ago.
> Compiler is gcc version 3.2 20020927 (prerelease), this is the version=20
> that was included in the cygwin distribution.
>=20
> and i forgot: in io.c it dumps core because dfd is null (fprintf(dfd,=20
> "%s", va_buf);) in io_debug_write

Ok, I know what the problem is now. It seems as if cgdb can't create the
home directory in XP. I'll have to inspect why cgdb does not die
gracefully.

> Another short question: Is it possible to automate the :set sc ?

Not yet. A planned feature that I think Mike will be working on for the
next release is a .cgdbrc file. That will provide you with what you
want.

Mike or Peter, I know we have talked about it. Did either of you plan on
adding that feature for the next release?

Thanks for the reports,
Bob Rossi

Re: [Cgdb-devel] compile for cygwin

[Mike M. <mmu...@cs...>]

Yes, I'm planning on doing the config file.  I was going to work on 
help first, but it doesn't matter which I do next.  We have another 
bug to look at, too.  I'll talk to you when you're back.

Mike

On Tue, 18 Mar 2003, Bob Rossi wrote:

:On Tue, Mar 18, 2003 at 11:16:39PM +0100, Armin Diehl wrote:
:> Bob,
:> 
:> >What compiler are you using to compile cgdb?
:> >What OS are you running?
:> 
:> The machine where i compiled and got the segfault was xp, cygwin was 
:> installed a few days ago.
:> Compiler is gcc version 3.2 20020927 (prerelease), this is the version 
:> that was included in the cygwin distribution.
:> 
:> and i forgot: in io.c it dumps core because dfd is null (fprintf(dfd, 
:> "%s", va_buf);) in io_debug_write
:
:Ok, I know what the problem is now. It seems as if cgdb can't create the
:home directory in XP. I'll have to inspect why cgdb does not die
:gracefully.
:
:> Another short question: Is it possible to automate the :set sc ?
:
:Not yet. A planned feature that I think Mike will be working on for the
:next release is a .cgdbrc file. That will provide you with what you
:want.
:
:Mike or Peter, I know we have talked about it. Did either of you plan on
:adding that feature for the next release?
:
:Thanks for the reports,
:Bob Rossi
:

Re: [Cgdb-devel] compile for cygwin

[Peter K. <pe...@ko...>]

After I finish unpacking I should have some time to continue looking at
the config stuff.  I plan on getting key-bindings in there next.

- Peter

On Tue, Mar 18, 2003 at 05:47:17PM -0500, Mike Mueller wrote:
> Yes, I'm planning on doing the config file.  I was going to work on=20
> help first, but it doesn't matter which I do next.  We have another=20
> bug to look at, too.  I'll talk to you when you're back.
>=20
> Mike
>=20
> On Tue, 18 Mar 2003, Bob Rossi wrote:
>=20
> :On Tue, Mar 18, 2003 at 11:16:39PM +0100, Armin Diehl wrote:
> :> Bob,
> :>=20
> :> >What compiler are you using to compile cgdb?
> :> >What OS are you running?
> :>=20
> :> The machine where i compiled and got the segfault was xp, cygwin was=
=20
> :> installed a few days ago.
> :> Compiler is gcc version 3.2 20020927 (prerelease), this is the version=
=20
> :> that was included in the cygwin distribution.
> :>=20
> :> and i forgot: in io.c it dumps core because dfd is null (fprintf(dfd,=
=20
> :> "%s", va_buf);) in io_debug_write
> :
> :Ok, I know what the problem is now. It seems as if cgdb can't create the
> :home directory in XP. I'll have to inspect why cgdb does not die
> :gracefully.
> :
> :> Another short question: Is it possible to automate the :set sc ?
> :
> :Not yet. A planned feature that I think Mike will be working on for the
> :next release is a .cgdbrc file. That will provide you with what you
> :want.
> :
> :Mike or Peter, I know we have talked about it. Did either of you plan on
> :adding that feature for the next release?
> :
> :Thanks for the reports,
> :Bob Rossi
> :
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink?=20
> You could win a Tablet PC. Get a free Tablet PC hat just for playing.=20
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> _______________________________________________
> Cgdb-devel mailing list
> Cgd...@li...
> https://lists.sourceforge.net/lists/listinfo/cgdb-devel

--=20
Peter D. Kovacs <pe...@ko...>

Re: [Cgdb-devel] compile for cygwin

[Bob R. <bob...@co...>]

On Tue, Mar 18, 2003 at 01:56:14PM +0100, Armin Diehl wrote:
> Hi,
>=20
> i'm tying to compile for cygwin, the compile runs fine but the resulting=
=20
> cgdb.exe will core dump:
>=20
> This happens with the 0.2.3 version. I also tried the cvs version, it=20
> will not core dump but will print nonsense in the upper half of the=20
> screen and hangs after that.
>=20

Hi Armin,

I just recently fixed cgdb for cygwin with XP.
You can give it a shot out of cvs if you'd like.
Otherwise, cgdb-0.3.0 will be released probably within April.

Thanks,
Bob Rossi