All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mattia Belletti <mbellett@cs.unibo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Getting fault address from a SIGSEGV
Date: Sat, 19 Mar 2005 14:44:44 +0100	[thread overview]
Message-ID: <423C2CCC.9040809@cs.unibo.it> (raw)

Hi all, 

   For a project I'm working on, I would need to get the fault address of
a ptraced child, whose SIGSEGV I've caught. I've tried to dig in UML 
source code to get how this is done, but I get lost after having 
followed the chain segv_handler <- sig_info <- sig_handler_common_tt <-
"r = &TASK_REGS(get_current())->tt;", since there the status I was 
looking for is stored in the thread_struct.regs, but I don't know where 
in the code such status is filled, and so where such information is 
taken from :-)
 

Hope you can light my way through the code ;-) 


-- 
Mat/tia Belletti             - Graduate student @ cs.unibo.it
ICQ: 33292311                - email: mbellett@cs.unibo.it
IRC: RedGlow                 - site(s): http://mbellett.web.cs.unibo.it/
RedGlow@jabber.linux.it/Gaim - Linux user 299762 @ machine 213003


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
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:[~2005-03-19 13:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-19 13:44 Mattia Belletti [this message]
2005-03-19 19:57 ` [uml-devel] Getting fault address from a SIGSEGV Jeff Dike

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=423C2CCC.9040809@cs.unibo.it \
    --to=mbellett@cs.unibo.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.