Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Steven J. Hill" <sjhill@cotw.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: binutils@sourceware.cygnus.com, linux-mips@oss.sgi.com
Subject: Re: Corrupted symbols for MIPS debugging...
Date: Thu, 13 Sep 2001 15:00:59 -0500	[thread overview]
Message-ID: <3BA1107B.B585E570@cotw.com> (raw)
In-Reply-To: 20010913130354.A29649@lucon.org

"H . J . Lu" wrote:
> 
> > (gdb) target remote /dev/ttyS1
> > Remote debugging using /dev/ttyS1
> > 0x80012828 in breakinst () at af_packet.c:1879
> > 1879            sock_unregister(PF_PACKET);
> > (gdb) bt
> > #0  0x80012828 in breakinst () at af_packet.c:1879
> > #1  0x8001a0d4 in sys_create_module (name_user=0x10001dc8 "cfi_probe",
> >     size=8176) at module.c:305
> 
> Please provide
> 
> (gdb) list breakinst
> (gdb) print breakinst
> 
(gdb) target remote /dev/ttyS1
Remote debugging using /dev/ttyS1
0x80012828 in breakinst () at af_packet.c:1879
1879            sock_unregister(PF_PACKET);
(gdb) list breakinst
1874
1875    static void __exit packet_exit(void)
1876    {
1877            remove_proc_entry("net/packet", 0);
1878            unregister_netdevice_notifier(&packet_netdev_notifier);
1879            sock_unregister(PF_PACKET);
1880            return;
1881    }
1882
1883    static int __init packet_init(void)
(gdb) print breakinst
$1 = {<text variable, no debug info>} 0x80012824 <breakinst>
(gdb) c
Continuing.



-- 
 Steven J. Hill - Embedded SW Engineer

  reply	other threads:[~2001-09-13 20:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-13 19:42 Corrupted symbols for MIPS debugging Steven J. Hill
2001-09-13 20:03 ` H . J . Lu
2001-09-13 20:00   ` Steven J. Hill [this message]
2001-09-13 20:13     ` H . J . Lu

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=3BA1107B.B585E570@cotw.com \
    --to=sjhill@cotw.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=hjl@lucon.org \
    --cc=linux-mips@oss.sgi.com \
    /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