Problem with error_start

[Egor Duda]

Hi!

Tuesday, 05 December, 2000 Trevor Forbes trevorforbes@ozemail.com.au wrote:

TF> I am having problem getting error_start=f:\home\bin\gdb.exe to work
TF> correctly.

TF> It seems that gdb will not start unless it is in the /bin directory. Ok, DJ
TF> has answered this before, in that, it is looking for  /share/gdbtcl based on
TF> where GDB is located.

TF> Well, how do I get GDB to work outside the /bin directory which, from what I
TF> understand, is the way to use error_start to debug Cygwin using a debug
TF> cygwin1.dll??

TF> I have tried setting TCL_LIBRARY=f:/Cygwin/usr/share/gdbtcl and
TF> GDBTK_LIBRARY=f:/Cygwin/usr/share/gdbtcl in the windows env but nothing
TF> seems to work? I seem to be missing something obvious?

TF> I am using  gdb-20001125-1 on win2000 and have CYGWIN=binmode ntsec tty
TF> error_start=f:\home\bin\gdb.exe

have  you  tried  starting  f:\home\bin\gdb.exe  from "windows command
prompt   (from  cmd.exe)?  This  should  be (almost) equivalent to the 
way  cygwin1.dll starts program specified in error_start. You can also
try  running text-mode version of  gdb:  'f:\home\bin\gdb.exe -nw'. if
this  works  from  command  prompt,  then  you  can  create batch file
f:\home\bin\error_start.cmd with a single line in it:

f:\home\bin\gdb.exe -nw %1 %2

and set CYGWIN=binmode ntsec tty error_start=f:\home\bin\error_start.cmd

Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19