All of lore.kernel.org
 help / color / mirror / Atom feed
From: Allan Graves <allan.graves@oracle.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] gdb ignoring skas breakpoints?
Date: Fri, 26 Aug 2005 21:49:51 -0400	[thread overview]
Message-ID: <430FC6BF.2020806@oracle.com> (raw)

Jeff,
I thought i had this thread trace thing several times, but I couldn't 
get gdb to stop on breakpoints, its like it was ignoring them....   it 
thought everything was in thread_info.h.  And it listed the right code, 
and i could do like b 26, and it would set a breakpoint for line 26 of 
the correct function with the correct filename, and then just ignore it. 

(gdb) info b
Num Type           Disp Enb Address    What
1   breakpoint     keep y   0x0806f607 in panic at kernel/panic.c:74
2   breakpoint     keep y   0x0805c254 in switch_to_skas at 
arch/um/kernel/skas/process_kern.c:29
3   breakpoint     keep y   0x081e5ac5 in schedule at thread_info.h:50
4   breakpoint     keep y   0x081e6037 in schedule at kernel/sched.c:2747



Any suggestions?
Allan


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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-08-27  1:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-27  1:49 Allan Graves [this message]
2005-08-27  9:26 ` [uml-devel] gdb ignoring skas breakpoints? Blaisorblade
2005-08-28 13:40   ` 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=430FC6BF.2020806@oracle.com \
    --to=allan.graves@oracle.com \
    --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.