using the 'call' command

[Martin Rivers]

When I use the 'call' command in my application, I get the message:

Breakpoint 1, I_CopyPath (p0=0x11b4720) at ./../../../../page4/xi/paths.c:632
(gdb) call I_DumpPath(p0)

Breakpoint 1, I_CopyPath (p0=0x11b4720) at ./../../../../page4/xi/paths.c:632
The program being debugged stopped while in a function called from GDB.
When the function (I_DumpPath) is done executing, GDB will silently
stop (instead of continuing to evaluate the expression containing
the function call).
(gdb)


I am using 5.3 of gdb and running this on a Sun Solaris system.  When using gdb
5.0,
I do not receive this message and printf's from the 'call'ed subroutine are
emitted.

Using the call command on a simple program works as I would expect, it is only
on
the application of interest I get this message from gdb (isn't it always the
way).

Any suggestions would be more than welcome.  Thanks in advance.