You received a segmentation fault, and these numbers are printed by the segfault handler of Zorp. Try running Zorp within gdb and check the backtrace when the segfault occurs. The dynamic linker also sends a segfault when two different versions of the same library is used. On Fri, Jun 13, 2003 at 12:48:16PM -0400, Philippe Lucas wrote:
I add -lz but, now I have a new error :
Jun 13 07:49:13 bridge zorp_http[12247]: (zorp@site/intra_http:0/http): Signal (11) received, stackdump follows; Jun 13 07:49:13 bridge zorp_http[12247]: (zorp@site/intra_http:0/http): Fatal signal occurred, dumping stack; eax='00000000', ebx='00000000', ecx='00000000', edx='00000000', esi='00000000', edi='00000000', eip='00000000' Jun 13 07:49:13 bridge zorp_http[12247]: (zorp@site/intra_http:0/http): retaddr=0x0, ebp=0x0 Jun 13 07:49:13 bridge zorp_http[12247]: (zorp@site/intra_http:0/http): 08048000-0804b000 r-xp 00000000 03:42 288358 /usr/local/lib/zorp/zorp Jun 13 07:49:13 bridge zorp_http[12247]: (zorp@site/intra_http:0/http): 0804b000-0804c000 rw-p 00002000 03:42 288358 /usr/local/lib/zorp/zorp
How can I have a better error message ?
Philippe Lucas
_______________________________________________ zorp mailing list zorp@lists.balabit.hu http://lists.balabit.hu/mailman/listinfo/zorp
-- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1