9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] rb kernel vs acid
Date: Sun,  4 Aug 2013 21:07:15 -0400	[thread overview]
Message-ID: <05f8e870a7dacf879f2aacd7e5b0bf7f@brasstown.quanstro.net> (raw)

if i type src(main) when debugging a routerboard
kernel, i get rather puzzling output

	; acid 9rb
	9rb:mips ELF32 executable
	/sys/lib/acid/port
	/sys/lib/acid/mips
	acid; src(main)
	no source for ?file?	# fileline (see symbol(2))

this is especially odd since ktrace does work, acid
does appear to disassemble correctly, map() appears
to be reasonable and e.g., /bin/cat works as expected.

does anyone else see this, too?

by the way there is a patch for the type skew
in symbol(2): /n/sources/patch/mach-man-type

- erik



             reply	other threads:[~2013-08-05  1:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-05  1:07 erik quanstrom [this message]
2013-08-05  4:59 ` David du Colombier
2013-08-05  5:04   ` erik quanstrom

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=05f8e870a7dacf879f2aacd7e5b0bf7f@brasstown.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).