Has anyone else ever noticed that running an Interbase program in the
debugger and then starting up another Interbase program causes the first
program to stop running? If I start up one command in an xterm like this:

[brad@dragon Quasar]$ gdb /opt/interbase/bin/isql
(gdb) run test.gdb

And then try to run another isql command to the same database in another
xterm, the first one breaks out to the gdb debugger like this:

Starting program: /opt/interbase/bin/isql test.gdb
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
Database: test.gdb
SQL>
Program received signal ?, Unknown signal.
0x402af544 in read () from /lib/libc.so.6
(gdb)

Here is the backtrace when it occurs:

(gdb) bt
#0 0x402af544 in read () from /lib/libc.so.6
#1 0x402fb8e0 in __check_rhosts_file () from /lib/libc.so.6
#2 0x40266e0b in _IO_file_underflow () from /lib/libc.so.6
#3 0x40268e9b in _IO_default_uflow () from /lib/libc.so.6
#4 0x40268205 in __uflow () from /lib/libc.so.6
#5 0x40265241 in getc () from /lib/libc.so.6
#6 0x80554d8 in get_statement ()
#7 0x80530da in do_isql ()
#8 0x804feab in ISQL_main ()
#9 0x805c00d in main ()
#10 0x40231cbe in __libc_start_main () from /lib/libc.so.6

The second isql program hangs while the debugger is still running but
continues on once the debugger quits running the program.

Odd no?!

PS: this is all on Linux using Mandrake 7.2, Firebird 0.9-4, and gdb 5.0

--
Brad Pepers
brad@...