Re: SIGSEGV Segmentation fault with 1.1.5 ) (more info)

2000-09-06 Thread Jean-Marc Lasgouttes
> "Sasa" == Sasa Janiska <[EMAIL PROTECTED]> writes: Sasa> Here I'm sending more information in the attached file. Sasa> Sincerely, Sasa You backtrace starts with #1 0x4023413f in buffered_vfprintf (s=0x402d17e0, format=0x40087758 "%s%s\n",args=0xbfffe978) at vfprintf.c:1767 #2 0x4022fb2

Re: SIGSEGV Segmentation fault with 1.1.5 ) (more info)

2000-08-31 Thread Sasa Janiska
On Thu, 31 Aug 2000, Allan Rae wrote: Thank you very much for your info. Here I'm sending more information in the attached file. Sincerely, Sasa (gdb) bt #0 0x402b01c8 in main_arena () from /lib/libc.so.6 #1 0x40215f7b in buffered_vfprintf (s=0x402b0120, format=0x4007e9f4 "%s%s\n", ar

Re: SIGSEGV Segmentation fault with 1.1.5

2000-08-30 Thread Allan Rae
On Wed, 30 Aug 2000, Sasa Janiska wrote: > Can I use some other debugging parameter to be able to provide you with > some more informations? When it crashes in gdb do this: (where (gdb) is the gdb prompt) (gdb) bt (gdb) up repeat the `up` a few times till you reach some code with debugging symb

SIGSEGV Segmentation fault with 1.1.5

2000-08-30 Thread Sasa Janiska
On my desktop I use two user accounts (besides root account) for different purposes. On one account where I work on one book, LyX (1.1.5) is generating SIGSEGV Segmentation fault. Here is the output from debugger: Program received signal SIGSEGV, Segmentation fault. 0x10 in ?? () Current langua