bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: info core dump when used with GNU screen


From: Zhang Shu
Subject: Re: info core dump when used with GNU screen
Date: Tue, 14 Dec 2004 10:45:04 +0900 (JST)

Hi Karl,

I tried 4.7.91 but it crashed again. Here is the gdb
backtrace:

Program received signal SIGABRT, Aborted.
0x2810dfc4 in kill () from /usr/lib/libc.so.4
(gdb) bt
#0  0x2810dfc4 in kill () from /usr/lib/libc.so.4
#1  0x2814f93e in abort () from /usr/lib/libc.so.4
#2  0x8068231 in memory_error_and_abort (fname=0x806d92e "xrealloc")
    at xmalloc.c:29
#3  0x80682c9 in xrealloc (pointer=0x808e200, bytes=29123) at xmalloc.c:56
#4  0x8053db9 in replace_in_documentation (
    string=0x806ae60 "Welcome to Info version %s. Type \\[get-help-window] for 
help, \\[menu-item] for menu item.", help_is_only_window_p=0) at infodoc.c:1030
#5  0x805a0d7 in display_startup_message_and_start () at session.c:161
#6  0x805a0b0 in begin_info_session (initial_node=0x8072120) at session.c:153
#7  0x805202c in main (argc=1, argv=0xbfbff058) at info.c:507
(gdb) 

ps. also tried the newest version of screen, but the result
was the same.

Thanks.

--
Zhang Shu



From: address@hidden (Karl Berry)
Subject: Re: info core dump when used with GNU screen
Date: Mon, 13 Dec 2004 09:06:41 -0500
Message-ID: <address@hidden>

>     I am using texinfo 4.6 on a FreeBSD 4.10-RELASESE-p3 box. I
>     found when I tried to use it with GNU screen (version
>     4.00.02), it died by generating cores dump. The terminal
>     variable was "screen".
> 
> Thanks for the report.
> 
> I can't reproduce this it the current sources, so maybe it's been fixed.
> I don't have the same version of screen, though.
> 
> So, can you please try the latest pretest from
> ftp://alpha.gnu.org/gnu/texinfo?  (Currently 4.7.91.)
> 
> If it still crashes, can you run info under gdb, and get a backtrace?
> Just say bt to gdb after the crash.  Hopefully that will provide enough
> info to find the bug.
> 
> Thanks,
> karl




reply via email to

[Prev in Thread] Current Thread [Next in Thread]