At 02:53 PM 5/21/00 -0400, you wrote:
>What do you mean. Right now you get both the filename and line
>number. Isn't that enough?
>
I was believing the subject was trace ? Here is what was in Andi's first post:
FIXME( "FATAL: Need to relocate %s, but no relocation records present
(%s). Try to run that file directly !\n",
So I think it's about trace, not *crashes*, right ?
If yes, where do you see a filename and a line number in what follows:
err:module:BUILTIN32_dlopen failed to load libborlndmm.fr.so: libborlndmm.fr.so:
cannot open shared object file: Aucun fichier ou r_pertoire de ce type.
err:module:BUILTIN32_dlopen failed to load libborlndmm.fr.so: libborlndmm.fr.so:
cannot open shared object file: Aucun fichier ou r_pertoire de ce type.
Can't open MIDI device '/dev/sequencer', errno 19 (Op_ration non support_e par ce
p_riph_rique.) !
err:module:BUILTIN32_dlopen failed to load libvclx35.fra.so: libvclx35.fra.so: cannot
open shared object file: Aucun fichier ou r_pertoire de ce type.
There is the function name, that's all. No line number than I can see.
If coders are careful to always precede the internal name with an prefix that is
unique to a file, it can work. If it's not possible, or if there are internal routines
with the
same names in different files, it can be annoying. Sometimes it's not obvious where a
particular error message has been generated.
Btw, for your question about my doc patch, Eric answered already; also I think
using a local repository would result in less work to do for the server.
Gerard
