fringe arrow conflict between compile and gud?

[JUAN-LEON Lahoz Garcia]

Hi,

I have:

(setq next-error-highlight 'fringe-arrow)

If I find error while compiling, next-error put a fringe arrow in the
error line. If I fix the error and compile again, the fringe arrow
does not dissapear (I do not if this is intended to be this way).

If the I open a gud session, I cannot track execution on file where
compilation fringe arrow is (I suppose some sort of conflict occurs).

Sometimes an error occurs:

Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
  set-window-point(#<window 382 on *Backtrace*> nil)
  gud-display-line("/home/leon/Testing/C/foo.c" 2182)
  gud-display-frame()
  gud-filter(#<process gud-a.out> 
"/home/leon/Testing/C/foo.c:2182:59257:beg:0x805663b\n")

And sometimes no error, but "next" and "step" gud commands do not
scroll to line where program execution is.

Of course these problems dissapear as soon I reload source file where
fringe arrow was.

--
juanleon