All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Dharm <mdharm@momenco.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Linux-MIPS <linux-mips@oss.sgi.com>
Subject: Re: Is this a toolchain bug?
Date: Sun, 24 Feb 2002 18:30:51 -0800	[thread overview]
Message-ID: <20020224183051.B17291@momenco.com> (raw)
In-Reply-To: <20020223210608.A1424@nevyn.them.org>; from dan@debian.org on Sat, Feb 23, 2002 at 09:06:08PM -0500

Okay, so I added that flag, and it actually seems to be correct.

But, the question remains, why does accessing that variable cause a
problem?  I'm going to do some more digging when I'm in the office
tomorrow, but one of the tests I already did was to put

e1000_proc_dev = NULL;

at one point in the code.  That line caused a crash with what looked like a
NULL-ptr dereference.

I'm going to re-examine this tomorrow, but I'm wondering if any of the
people on this list that are using this driver have CONFIG_PROC_FS turned
on.

Matt

On Sat, Feb 23, 2002 at 09:06:08PM -0500, Daniel Jacobowitz wrote:
> On Fri, Feb 22, 2002 at 05:57:08PM -0800, Matthew Dharm wrote:
> > If this is user-error, I'd love to know what I'm doing wrong.  If this
> > is a toolchain bug, who do I report this to?
> 
> User error, at least what you've described.  Add the -r flag to the
> objdump command line, or look at a statically linked object.
> 
> -- 
> Daniel Jacobowitz                           Carnegie Mellon University
> MontaVista Software                         Debian GNU/Linux Developer

-- 
Matthew Dharm                              Work: mdharm@momenco.com
Senior Software Designer, Momentum Computer

  reply	other threads:[~2002-02-25  3:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-23  1:57 Is this a toolchain bug? Matthew Dharm
2002-02-24  2:06 ` Daniel Jacobowitz
2002-02-25  2:30   ` Matthew Dharm [this message]
2002-02-25 18:36 ` Kevin Paul Herbert
2002-02-25 19:54   ` Matthew Dharm
2002-02-25 20:30   ` Matthew Dharm
2002-02-26  1:13     ` Daniel Jacobowitz
2002-02-26  1:18       ` Matthew Dharm
2002-02-26 10:31     ` Tommy S. Christensen
2002-02-26 20:29       ` Matthew Dharm

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=20020224183051.B17291@momenco.com \
    --to=mdharm@momenco.com \
    --cc=dan@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.