3.6p2 build errors on buffer_get with latest portable/SNAP

Darren Tucker dtucker at zip.com.au
Fri Sep 12 12:31:01 EST 2003


"STEWARD, Curtis (Jamestown)" wrote:
> I'm new to some of this so bear with me, I did post a
> buffer_get() error but while debugging I could make it fail
> on buffer_init() 31, weird.  Here's the bt without
> the continue:

> (gdb) bt
> #0  buffer_get (buffer=0xbffff210, buf=0x0, len=1) at buffer.c:124
> #1  0x00000000 in ?? ()

Hmm, there should be more here, I don't know what there isn't.

Plan B: if you insert an abort(); immediately before the fatal at
buffer.c:124 then run it normally, you should get a core dump which you
can generate the backtrace from.  It should look something like this:

# ./sshd -t
[core dumps]
# gdb -q ./sshd core
Core was generated by `./sshd -t'.
[snip]
#0  0x4020bfd1 in kill () from /lib/libc.so.6
(gdb) bt
#0  0x4020bfd1 in kill () from /lib/libc.so.6
#1  0x4020bc94 in raise () from /lib/libc.so.6
#2  0x4020d04d in abort () from /lib/libc.so.6
#3  0x08062bd7 in buffer_get () at ../buffer.c:123
#4  0x08062a1c in buffer_get_char (buffer=0xbfffd4f0) at ../bufaux.c:262
#5  0x08061ac5 in key_load_public_rsa1 (fd=3,
    filename=0x8079e80 "/usr/local/etc/ssh_host_rsa_key", commentp=0x0)
    at ../authfile.c:268
#6  0x080622f3 in key_load_private (
    filename=0x8079e80 "/usr/local/etc/ssh_host_rsa_key",
    passphrase=0x8078c1a "", commentp=0x0) at ../authfile.c:573
#7  0x0804d8ae in main (ac=2, av=0x8092f68) at ../sshd.c:978
#8  0x401fa4ed in __libc_start_main () from /lib/libc.so.6

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.




More information about the openssh-unix-dev mailing list