Q. When using avs_dbx under Red Hat Linux I received the follwing error.

Program received signal SIGSEGV, Segmentation fault.
0x4013197b in _IO_vfprintf (s=0x80acb88,
     format=0x80a2ec0 "%s: AVS_DBX Initialization\n", ap=0xbffff644)
     at vfprintf.c:1048
1048    vfprintf.c: No such file or directory.

A. This issue may be caused by an interface of gdb to avs. You can resolve this by downloading the AVSlinuxLib.tar file.

1. Create a new directory in your avs installation directory or home directory called avs_dbx_libs(this name is just a suggestion)
2. Copy the files from <avs install>/lib to the directory you created.
3. Download the AVSLinusLib.tar and place them into the avs_dbx_libs directory
4. Un-tar the lib files into the avs_dbx_libs directory. Allow it to overwrite the files.
   WARNING: do not overwrite the files in the <avs install>/lib directory. If you do the only way to get back will be to reinstall AVS5

In order to use these new libraries you will need to recompile your module with the -g for debugging and ensure you set the lib to the new directory. If you are using the our Makefile for a prototype you most likely can set the variable AVS_LIBS to the path to avs_dbx_libs directory.

With these libraries, the gdb will start in the libflow of avs5. This changes the method of setting breakpoints for your module. The best bet is to set an initial breakpoint in your compute or description function, as in:
(gdb) break my_compute

then run. Once it breaks, the context is now set to your immediate file so
(gdb) break 283

should work relative to your file.