Re: pkg/54348: pkgsrc net/fetch core dumps

[Hiroshi Hakoyama <hiroshi-hakoyama%nagano.ac.jp@localhost>]

Dear David,

> so, for the time being at least, I don't understand... if you can
> build with debug info that's probably the best way to move forward.

I build fetch with -g -O0.
Please see the following gdb output. If you request me to type some additional commands, I will do.

Hiroshi


# gdb fetch
GNU gdb (GDB) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "sparc-sun-solaris2.10".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from fetch...(no debugging symbols found)…done.

(gdb) run https://ftp.netbsd.org/pub/pkgsrc/distfiles/libunistring-0.9.10.tar.gz
Starting program: /usr/pkg/bin/fetch https://ftp.netbsd.org/pub/pkgsrc/distfiles/libunistring-0.9.10.tar.gz
[Thread debugging using libthread_db enabled]
[New Thread 1 (LWP 1)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1 (LWP 1)]
0x0001660c in fetchXGet ()

(gdb) break main
Breakpoint 1 at 0x156ec

(gdb) next
Single stepping until exit from function fetchXGet,
which has no line number information.
procfs: couldn't find pid -1 in procinfo list.



> 2019/07/14 6:20、David Holland <dholland-pbugs%netbsd.org@localhost>のメール:
> 
> The following reply was made to PR pkg/54348; it has been noted by GNATS.
> 
> From: David Holland <dholland-pbugs%netbsd.org@localhost>
> To: gnats-bugs%netbsd.org@localhost
> Cc: 
> Subject: Re: pkg/54348: pkgsrc net/fetch core dumps
> Date: Sat, 13 Jul 2019 21:17:27 +0000
> 
> On Thu, Jul 11, 2019 at 11:20:01AM +0000, Hiroshi Hakoyama wrote:
>>> does the libfetch package match the fetch package?
>> Yes. I build fetch and libfetch after a new bootstrap.
> 
> ok, then that's not the problem...
> 
>>> The important part here is probably not that it's Solaris but that
>>> it's sparc, and the code has probably done something either
>>> endian-dependent or that violates proper integer alignment.
>> 
>> Recently, I changed the IP address of the server from a global one to a =
>> local one.
>> I may break some configurations in the process.
> 
> None of the code near the stack trace looks like it should depend on
> that.
> 
> so, for the time being at least, I don't understand... if you can
> build with debug info that's probably the best way to move forward.
> 
> -- 
> David A. Holland
> dholland%netbsd.org@localhost
>