From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Limpach Subject: Re: anybody using pdb? Date: Fri, 12 Mar 2004 16:10:49 +0100 Sender: xen-devel-admin@lists.sourceforge.net Message-ID: <177501c40845$123fe740$070414ac@pin> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Return-path: Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Keir Fraser Cc: xen-devel@lists.sourceforge.net List-Id: xen-devel@lists.xenproject.org > Okay, I checked in a fix somewhat like the one you initially > proposed. Fancy giving it another spin? :-) Ok, this works. Thanks! And breakpoints now work occasionally... I think the problem is that my test machine is 2-CPU SMP: (from a log of the 'wire' between gdb and Xen, Xen->gdb is in [], everything else is gdb->Xen) $Mfc510390,1:cc#a5[+][$][O][K][#][9][$][S][a][0] Here gdb sets the breakpoint by writing 0xcc to the breakpoint address. Xen then would acknowledge this by replying with OK by sending "+$OK#9a" but it doesn't get to entirely send the reply since I guess the breakpoint is hit on the other CPU? (the breakpoint is on __enter_scheduler btw) The log should look like this: $Mfc510390,1:cc#a5[+][$][O][K][#][9][a]+$Hc0#db[+][$][O][K][#][9][a]+$C0a#d4 [+][$][S][0][5][#][b][8]+ Here the reply works and gdb sends commands Hc0 and C0a to continue execution and only then Xen hits the breakpoint and sends $S05#b8 which gdb then acknowledges with a +... I guess we'd have to IPI the other CPUs when we hit a breakpoint? christian ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click