Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#992471: segmentation fault with "info -a ..."

20 views
Skip to first unread message

Bjarni Ingi Gislason

unread,
Aug 18, 2021, 10:20:03 PM8/18/21
to
Package: info
Version: 6.7.0.dfsg.2-6
Severity: normal


Dear Maintainer,

* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?

"info -a automake" and "info -a bash"

* What was the outcome of this action?

info[9461]: segfault at 40 ip 0000557548b827ee sp 00007fffef0e70f0 error
4 in info[557548b78000+34000]
Code: df e8 36 fe ff ff 85 c0 74 ae 48 8b 3d bb cd 03 00 48 85 ff 74 a2
5b e9 90 fb ff ff 41 57 41 56 41 55 41 54 55 53 48 83 ec 18 <48> 8b 5f
40 89 54 24 0c 48 85 db 0f 84 92 00 00 00 4c 8b 23 4d 85
Segmentation fault

-- System Information:
Debian Release: 11.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.46-4 (SMP w/2 CPU threads)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages info depends on:
ii install-info 6.7.0.dfsg.2-6
ii libc6 2.31-13
ii libtinfo6 6.2+20201114-2

info recommends no packages.

info suggests no packages.

-- no debconf information

--
Bjarni I. Gislason

Norbert Preining

unread,
Aug 19, 2021, 1:20:03 AM8/19/21
to
Hi

> "info -a automake" and "info -a bash"
>
> info[9461]: segfault at 40 ip 0000557548b827ee sp 00007fffef0e70f0 error
> 4 in info[557548b78000+34000]

Not reproducible here.

Can you run it in a gdb session
$ gdb info
...
(gdb) set args -a automake
(gdb) run
...

Then it should return at the segfault, and you can type
bt
for backtrace and capture the output.

Best

Norbert

--
PREINING Norbert https://www.preining.info
Fujitsu Research + IFMGA Guide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Norbert Preining

unread,
Aug 19, 2021, 10:20:04 AM8/19/21
to
Hi Bjarni,

> (No debugging symbols found in info)

ARggh, there was something I forgot.

Before running gdb, please do
export DEBUGINFOD_URLS=https://debuginfod.debian.net
to get the debug symbols downloaded. Otherwise no use.

Thanks

Bjarni Ingi Gislason

unread,
Aug 19, 2021, 10:20:04 AM8/19/21
to
On Thu, Aug 19, 2021 at 02:04:40PM +0900, Norbert Preining wrote:
> Hi
>
> > "info -a automake" and "info -a bash"
> >
> > info[9461]: segfault at 40 ip 0000557548b827ee sp 00007fffef0e70f0 error
> > 4 in info[557548b78000+34000]
>
> Not reproducible here.
>
Debugging "info":

Reading symbols from info...
(No debugging symbols found in info)
(gdb) set args -a bash
(gdb) run
Starting program: /usr/bin/info -a bash

Program received signal SIGSEGV, Segmentation fault.
0x00005555555657ee in ?? ()
(gdb) bt
#0 0x00005555555657ee in ?? ()
#1 0x000055555555db18 in ?? ()
#2 0x000055555555bf6c in ?? ()
#3 0x00007ffff7df1d0a in __libc_start_main (main=0x55555555b830, argc=3, argv=0x7fffffffe168, init=<optimized out>,
fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffe158) at ../csu/libc-start.c:308
#4 0x000055555555d40a in ?? ()
(gdb) quit

--
Bjarni I. Gislason

Hilmar Preuße

unread,
Aug 19, 2021, 7:00:04 PM8/19/21
to
Hi,

no symbols here. Could you re-run, with the setting suggested by Norbert?

Hilmar

19.08.2021 16:18:18 Bjarni Ingi Gislason <bjar...@rhi.hi.is>:

Bjarni Ingi Gislason

unread,
Aug 19, 2021, 8:00:03 PM8/19/21
to
On Thu, Aug 19, 2021 at 11:08:17PM +0900, Norbert Preining wrote:
> Hi Bjarni,
>
> > (No debugging symbols found in info)
>
> ARggh, there was something I forgot.
>
> Before running gdb, please do
> export DEBUGINFOD_URLS=https://debuginfod.debian.net
> to get the debug symbols downloaded. Otherwise no use.
>
Reading symbols from info...
Reading symbols from /home/bg/.cache/debuginfod_client/7cad18c2c9b827ea78ed9e2c7bef73ce276f025c/debuginfo...
(gdb) set args -a bash
(gdb) run
Starting program: /usr/bin/info -a bash

Program received signal SIGSEGV, Segmentation fault.
0x00005555555657ee in info_get_menu_entry_by_label (node=node@entry=0x0, label=label@entry=0x5555555c2050 "bash",
sloppy=sloppy@entry=1) at info-utils.c:225
Download failed: Invalid argument. Continuing without source file ./info/info-utils.c.
225 info-utils.c: No such file or directory.
(gdb) bt
#0 0x00005555555657ee in info_get_menu_entry_by_label (node=node@entry=0x0, label=label@entry=0x5555555c2050 "bash",
sloppy=sloppy@entry=1) at info-utils.c:225
#1 0x000055555555db18 in dir_entry_of_infodir (label=label@entry=0x5555555c2050 "bash",
searchdir=0x5555555c1f10 "/usr/local/share/info") at dir.c:294
#2 0x000055555555bf6c in info_find_matching_files (filename=0x5555555c2050 "bash") at info.c:582
#3 main (argc=<optimized out>, argv=<optimized out>) at info.c:937
(gdb) quit

Probable cause is an empty "/usr/local/share/info/dir".
I was compiling the latest "automake" and "autoconf" and could not get
to see the corresponding info files with
INFOPATH=/usr/local/share/info:/usr/share/info:/home/bg/git/groff/build/doc

I do not know how to populate the "dir" directory, did not find
anything in the "info info" output.

To see the latest info-file I tried "info -f automake" and that showed
the new version.

Bjarni Ingi Gislason

unread,
Aug 19, 2021, 8:40:02 PM8/19/21
to
File "dir" is only readable by root and is not empy.
"automake" installed the latest file.

--
Bjarni I. Gislason

Norbert Preining

unread,
Aug 19, 2021, 8:40:03 PM8/19/21
to
Hi Bjarni,

thanks

> (gdb) bt
> #0 0x00005555555657ee in info_get_menu_entry_by_label (node=node@entry=0x0, label=label@entry=0x5555555c2050 "bash",
> sloppy=sloppy@entry=1) at info-utils.c:225
> #1 0x000055555555db18 in dir_entry_of_infodir (label=label@entry=0x5555555c2050 "bash",
> searchdir=0x5555555c1f10 "/usr/local/share/info") at dir.c:294
> #2 0x000055555555bf6c in info_find_matching_files (filename=0x5555555c2050 "bash") at info.c:582
> #3 main (argc=<optimized out>, argv=<optimized out>) at info.c:937
> (gdb) quit

Ok ... it shouldn't crash here indeed.

> Probable cause is an empty "/usr/local/share/info/dir".

> File "dir" is only readable by root and is not empy.
> "automake" installed the latest file.

You need to call
install-info FILE /usr/local/share/info/dir
for the .info FILE you installed

Also, make sure it is readable my world ..

Best

Hilmar Preuße

unread,
Mar 30, 2022, 4:40:04 PM3/30/22
to
Am 20.08.2021 um 01:49 teilte Bjarni Ingi Gislason mit:

Hi Bjarni,

has the issue been solved eventually in info 6.8?

Hilmar

> Program received signal SIGSEGV, Segmentation fault.
> 0x00005555555657ee in info_get_menu_entry_by_label (node=node@entry=0x0, label=label@entry=0x5555555c2050 "bash",
> sloppy=sloppy@entry=1) at info-utils.c:225
> Download failed: Invalid argument. Continuing without source file ./info/info-utils.c.
> 225 info-utils.c: No such file or directory.
> (gdb) bt
> #0 0x00005555555657ee in info_get_menu_entry_by_label (node=node@entry=0x0, label=label@entry=0x5555555c2050 "bash",
> sloppy=sloppy@entry=1) at info-utils.c:225
> #1 0x000055555555db18 in dir_entry_of_infodir (label=label@entry=0x5555555c2050 "bash",
> searchdir=0x5555555c1f10 "/usr/local/share/info") at dir.c:294
> #2 0x000055555555bf6c in info_find_matching_files (filename=0x5555555c2050 "bash") at info.c:582
> #3 main (argc=<optimized out>, argv=<optimized out>) at info.c:937
> (gdb) quit
>
> Probable cause is an empty "/usr/local/share/info/dir".
> I was compiling the latest "automake" and "autoconf" and could not get
> to see the corresponding info files with
> INFOPATH=/usr/local/share/info:/usr/share/info:/home/bg/git/groff/build/doc
>
> I do not know how to populate the "dir" directory, did not find
> anything in the "info info" output.
>
> To see the latest info-file I tried "info -f automake" and that showed
> the new version.
>


--
sigfault

OpenPGP_signature

Bjarni Ingi Gislason

unread,
Mar 30, 2022, 7:50:03 PM3/30/22
to
On Wed, Mar 30, 2022 at 10:32:16PM +0200, Hilmar Preuße wrote:
> Am 20.08.2021 um 01:49 teilte Bjarni Ingi Gislason mit:
>
> Hi Bjarni,
>
> has the issue been solved eventually in info 6.8?
>
Yes.

I suppose I did what Norbert suggested and that fixed it (?) (that is,
avoided the crash).

So the ticket can be closed as solved.

--
Bjarni I. Gislason
0 new messages