From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: pppd hangs on SIGHUP
Date: Thu, 21 Jan 2010 12:39:48 +0000 [thread overview]
Message-ID: <4B584B14.3080301@workingcode.com> (raw)
In-Reply-To: <8D.DA.01403.892965B4@cdptpa-omtalb.mail.rr.com>
Leslie Rhorer wrote:
> 2875: /usr/sbin/pppd call cricket
> (No symbols found)
> 0xb7f14424: ???? (8, 2, 808e580, bff2eaa8, 97aeea0, 97aeeb8)
> 0x08069654: ???? (8, ffffffff)
> 0x0806d751: ???? (807bee4, 0, 0, bff2eaf8, 808b884, ffffffff)
> 0x08062ca9: ???? (0, 0, 0, 806656f, 80813ae, 807c098) + 10
> 0x0805164b: ???? (80905e0, 80905e4, c, b3b, 0, c) + b0
> 0x0805226f: ???? (807bc70, 804f930, bff2ec38, b7d50455, 3, bff2ec64) + 50
> 0xb7d50455: ???? (8051890, 3, bff2ec64, 807bc70, 807bc60, b7f23250) +
> 400d13a8
Compiling pppd first with "-g" would probably have been a good idea. It
looks like this is a system call on fd 8, which is the modem device:
> pppd 2875 root 8u CHR 166,0 4814
> /dev/ttyACM0
... but that's just a guess.
> I am not deeply familiar with Linux. What is a good debugger
> available for it, preferably from a Debian mirror?
The GNU debugger 'gdb' is decent.
--
James Carlson 42.703N 71.076W <carlsonj@workingcode.com>
next prev parent reply other threads:[~2010-01-21 12:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 5:20 pppd hangs on SIGHUP Leslie Rhorer
2010-01-20 5:34 ` Bill Unruh
2010-01-20 5:43 ` James Cameron
2010-01-20 5:47 ` James Cameron
2010-01-20 5:53 ` Leslie Rhorer
2010-01-20 6:10 ` Leslie Rhorer
2010-01-20 12:25 ` James Carlson
2010-01-21 2:20 ` Leslie Rhorer
2010-01-21 2:47 ` Leslie Rhorer
2010-01-21 12:39 ` James Carlson [this message]
2010-01-21 15:19 ` Leslie Rhorer
2010-01-22 1:50 ` Leslie Rhorer
2010-01-22 2:13 ` James Cameron
2010-01-22 4:36 ` Leslie Rhorer
2010-01-23 17:40 ` Leslie Rhorer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B584B14.3080301@workingcode.com \
--to=carlsonj@workingcode.com \
--cc=linux-ppp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox