All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] UML/64bit is miscompiled by gcc 4.0.3 on Ubuntu 6.06 LTS
Date: Mon, 22 Jan 2007 15:59:45 -0500	[thread overview]
Message-ID: <20070122205945.GB5203@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200701200018.30165.blaisorblade@yahoo.it>

On Sat, Jan 20, 2007 at 12:18:30AM +0100, Blaisorblade wrote:
> Ok, I hope I remembered correctly how to debug such faults (I'm posting the 
> full procedure so you can give a look)

Correct.

> 0x00000000619a592f:     mov    %edx,%fs:(%rcx)  #faulting instruction.

This and the registers involved are usually all you need.

> RCX there is (long)regs->skas.regs[11] = -64, and for FS, since HOST_FS = 25,
> I get:
> 
> print/x regs->skas.regs[25]
> $45 = 0x63

The presence of %fs in the instruction immediately suggests a TLS problem.

Also, the trap number in cases like this should be 13, rather than the
14 you get with a normal page fault.

%fs isn't 0, so that's one thing that's not wrong.  What's in the
corresponding segment?

-- 
Work email - jdike at linux dot intel dot com

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2007-01-22 21:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17 16:15 [uml-devel] UML/64bit is miscompiled by gcc 4.0.3 on Ubuntu 6.06 LTS Blaisorblade
2007-01-17 18:17 ` Christopher S. Aker
2007-01-17 18:15   ` Antoine Martin
2007-01-17 19:50     ` Antoine Martin
2007-01-19 11:00       ` [uml-devel] buggy UML AMD64? Antoine Martin
2007-01-19 16:07         ` Daniel Gryniewicz
2007-01-19 16:14           ` Antoine Martin
2007-01-19 16:38             ` Daniel Gryniewicz
2007-01-19 16:42               ` Antoine Martin
2007-01-19 17:33                 ` Antoine Martin
2007-01-19 19:56                   ` Antoine Martin
2007-01-21  9:17                     ` Boaz Harrosh
2007-01-21 13:04                       ` Antoine Martin
2007-01-23 15:20                         ` Boaz Harrosh
2007-01-21 14:38                     ` Joel Palmius
2007-01-21 14:46                       ` Antoine Martin
2007-01-21 14:55                         ` Joel Palmius
2007-01-21 16:11                         ` Joel Palmius
2007-01-22 22:09                         ` Jeff Dike
2007-01-23  0:59                           ` Antoine Martin
2007-01-19 16:38             ` Antoine Martin
2007-02-15  3:43     ` [uml-devel] UML/64bit is miscompiled by gcc 4.0.3 on Ubuntu 6.06 LTS Blaisorblade
2007-01-19 23:31   ` Blaisorblade
2007-01-17 23:26 ` Jeff Dike
2007-01-19 23:18   ` Blaisorblade
2007-01-22 20:59     ` Jeff Dike [this message]
2007-01-23  8:09       ` Blaisorblade

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=20070122205945.GB5203@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=blaisorblade@yahoo.it \
    --cc=user-mode-linux-devel@lists.sourceforge.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 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.