Re: Cygnus gdb problem on Win95

[Wengui Su]

> 
> >>>>> "WS" == Wengui Su <address@hidden> writes:
> 
> WS> I experienced some problem with Cygnus gdb on Win95. I am running
> WS> gdb within emacs(actually I couldn't run gdb from bash because the
> WS> error with main.tcl).
> 
> What do you get if you do a:
> 
>   M-:
>   (getenv "GDBTK_LIBRARY")
> 

The value for GDBTK_LIBRARY is c:/Cygnus/B19/share/gdbtcl, which is right.

> Have you tried using the modified swarm.exe I posted to generate
> the elisp variable settings?
> 
> M-x gdb seems to work ok for me with the "swarm -e > vars.el" output, although
> unless you inherit a PATH with gdb.exe in it from the environment,
> you'd need to specify the full gdb path by hand or add it Emacs' exec-path,
> like so -- after doing a (load "/Swarm/vars.el").
> 
> (setq exec-path (append (list (concat (getenv "CYGROOT")
>                                       "\\H-i386-cygwin32\bin"))))

I didn't use yours swarm.exe since I already set up all of the neccesary 
environment variables in my autoexec.bat, which inherited by the bash when I 
start the shell within emacs, include the path to gdb.exe. Do I need to set up 
the things in emacs again? 

I add your's above line in my .emacs, and it disable the path, and I couldn't 
start gdb again anymore.

> WS> some variable value is right, but
> WS> some is unbelievable big. In order to track the problem down, I
> WS> swith on my Solaris system, and do the same thing with gdb, the
> WS> problem disappeared(same version of program). 
> 
> Maybe this is just the result of optimization?  Does it help to
> disable optimization by passing "OPTFLAGS=-O0" on the command line of
> `make' for a rebuild of your application and/or a recompile of Swarm itself?

I used the OPTFLAGS=-oo to recompile my application, but it didn't generate the 
object files(*.o) with that option anymore. OPTFLAGS=-OO(capital o) doesn't 
recognize by make.

Thank you


Wengui Su



                  ==================================
   Swarm-Support is for discussion of the technical details of the day
   to day usage of Swarm.  For list administration needs (esp.
   [un]subscribing), please send a message to <address@hidden>
   with "help" in the body of the message.
                  ==================================