On Thu, Aug 9, 2012 at 3:54 PM, wrote:
> Dear Mr. & Miss,
>
> Attached the panic log
>
> Thanks,
> Ban
>
> From: Ban Feng(馮冠中)
> Sent: Wednesday, August 08, 2012 2:24 PM
> To: 'kgdb-bugreport@lists.sourceforge.net'
> Subject: KGDB setup problem
>
> Dear Mr. & Miss,
>
> Thanks in advance your kind
On Tue, Jul 24, 2012 at 7:27 AM, shu wrote:
> Hi there,
> I need to debug an android phone with which using serial port is
> not convenient.
> So I consider writing a virtual tty driver which implements two
> connected virtual tty devices. kgdboc would be connected to tty1, tty2
> would
I think this problem have been fixed by
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=fb82c0ff27b2c40c6f7a3d1a94cafb154591fa80
On Wed, Mar 28, 2012 at 5:24 PM, Rahul Viradiya
wrote:
> Hi,
> ---
On Thu, Sep 22, 2011 at 3:50 PM, wrote:
> From: Dongdong Deng
>
> The CONFIG_DEBUG_RODATA will limit KGDB/KDB's set breakpoint function,
> and CONFIG_DEBUG_RODATA and CONFIG_KGDB could survive together.
>
> Thus most of new user of KGDB/KDB get the set_breakpo
On Thu, Sep 22, 2011 at 4:19 AM, Tim Bird wrote:
> This fixes a bug with setting a breakpoint during kdb initialization
> (from kdb_cmds). Any call to kdb_printf() before the initialization
> of the kgdboc serial console driver (which happens much later during
> bootup than kdb_init), results in
On Wed, Sep 21, 2011 at 12:43 AM, Tim Bird wrote:
> On 09/19/2011 07:38 PM, Dongdong Deng wrote:
>> On Tue, Sep 20, 2011 at 8:14 AM, Tim Bird wrote:
>>> I recently tried using KDB on a 3.0.1 kernel, on an x86 target, using
>>> a fairly-close-to-default kernel configur
On Tue, Sep 20, 2011 at 8:14 AM, Tim Bird wrote:
> I recently tried using KDB on a 3.0.1 kernel, on an x86 target, using
> a fairly-close-to-default kernel configuration.
>
> I found that I could not set a breakpoint.
> It sets inside KDB, but then fails to apply the breakpoint when
> resuming to
You can try the agent-proxy, it is maintained by Jason too,
git clone git://git.kernel.org/pub/scm/utils/kernel/kgdb/agent-proxy.git
Readme:
http://git.kernel.org/?p=utils/kernel/kgdb/agent-proxy.git;a=blob;f=README.TXT;h=07fa7f00949017652f7bbc645bdfa2948a8f0262;hb=HEAD
Example:
http://git.kerne
On Thu, Jun 30, 2011 at 8:30 AM, Tim Bird wrote:
> Hi all,
>
> I'm new to KDB, but I've been looking at the code and trying
> to document a few things. I couldn't find any documentation on a few
> kdb features (initialization commands, defcmd, supported environment vars,
> etc.)
> I wrote some u
bhu
>
>
> On Thu, May 19, 2011 at 6:45 AM, Dongdong Deng wrote:
>>
>> On Wed, May 18, 2011 at 7:23 PM, Prabhu nath
>> wrote:
>> > Dear All,
>> >
>> > There is a problem with the KGDB at the very first break point
>> > after
>
On Wed, May 18, 2011 at 7:23 PM, Prabhu nath wrote:
> Dear All,
>
> There is a problem with the KGDB at the very first break point after
> executing the gdb command "target remote /dev/ttyS0" from the host.
> I have verbatim, followed the KGDB document
> http://kernel.org/pub/linux/ker
On Fri, Apr 1, 2011 at 1:40 AM, Jason Wessel wrote:
> On 03/24/2011 12:24 AM, Cyrill Gorcunov wrote:
>> If Jason is ok with such splitting -- I dont mind either ;)
>>
>> On Thursday, March 24, 2011, Dongdong Deng wrote:
>>> On Thu, Mar 24, 2011 at 4:32 AM, Cyrill G
On Thu, Mar 24, 2011 at 4:32 AM, Cyrill Gorcunov wrote:
> kgdb needs IPI to be sent and handled before perf
> or anything else NMI, otherwise kgdb hangs with bootup
> self-tests (found on P4 HT SMP machine). Raise its priority
> so that we're called first in a notifier chain.
>
> Reported-by: Don
Commit dfee3a7b92208b30f77876068aece9ea571270c2(debug_core:
refactor locking for master/slave cpus) uses spin_lock to replace
the atomic counter lock mechanism, and most kgdb data was designed
to per-cpu, thus the 'smp_mb()' operation is useless here now.
Signed-off-by: Dongdong Deng
-
confused.
Add a memory barrier before atomic_inc(&slaves_in_kgdb) to
avoid that potential problem.
Signed-off-by: Dongdong Deng
---
kernel/debug/debug_core.c |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/kernel/debug/debug_core.c b/kernel/debug/debug_core.c
i
d the atomic_xchg().
Signed-off-by: Dongdong Deng
---
kernel/debug/debug_core.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/debug/debug_core.c b/kernel/debug/debug_core.c
index bec8af0..722968f 100644
--- a/kernel/debug/debug_core.c
+++ b/kernel/
Passing the address of current->thread.evr register to memcpy function.
Signed-off-by: Dongdong Deng
CC: Hai Shan
CC: Milton Miller
CC: linuxppc-...@lists.ozlabs.org
---
arch/powerpc/kernel/kgdb.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/ker
On Fri, Nov 5, 2010 at 1:44 PM, jovi zhang wrote:
> fix memory leak in kdb_main.c
>
> Signed-off-by: jovi zhang
> kernel/debug/kdb/kdb_main.c | 13 +++--
> 1 files changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/kernel/debug/kdb/kdb_main.c b/kernel/debug/kdb/kdb_main.c
> index
On Thu, Oct 14, 2010 at 9:34 PM, srikanth krishnakar
wrote:
>
> Hi Jason,
>
> Kernel: 2.6.30
> Branch used KGDB-2.6.30
>
> x86 target hangs after some simple steps in KGDB over Ethernet.
>
> //--Target side, console over minicom
> ...
> r...@em64t_pc_ru:~# sync
>
> //-- Host side. GDB.
> ...
>
r for
hw_breakpoint_handler() to decide to pass or stop the
DIE_DEBUG notification.
As KGDB set that flag, hw_breakpoint_handler() will pass
the DIE_DEBUG notification, thus kgdb have the chance
to take DIE_DEBUG notification.
Signed-off-by: Dongdong Deng
Reviewed-by: Bruce Ashfield
---
arch/x86/k
It is ok to me. :-)
Best Regards,
Dongdong
On Thu, Jun 17, 2010 at 5:33 PM, Andy Shevchenko
wrote:
> From: Andy Shevchenko
>
> Signed-off-by: Andy Shevchenko
> Cc: Jason Wessel
> Cc: Martin Hicks
> Cc: kgdb-bugreport@lists.sourceforge.net
> ---
> kernel/debug/gdbstub.c | 21 +-
Hi Jason,
Thanks for your sharing, It is very useful to us to learn and know how
to debug kernel. :-)
Dongdong
On Wed, Jun 23, 2010 at 5:02 AM, Jason Wessel
wrote:
>
> Normally I might consider this kind of thing spam, but I thought I would
> mention I am presenting a generic kernel debugging
Maybe contact the author of kdmx is a good way to solve your problem quickly.
Or debugging the kdmx by yourself to see what happens. :-)
Dongdong
2010/6/2 Ireneusz Szcześniak :
> Hi,
>
> In my RouterBOARD433 I only have a single serial port, which I want to
> use as a regular console and as a c
On Fri, May 28, 2010 at 4:58 PM, Lal wrote:
> I am trying to use kgdb over ethernet but gdb fails to connect to remote
> target.
>
> I noted that gdb packets are reaching to remote target and kgdboe is
> working as expected (through prints), however gdb does not receive
> packets back.
>
> I chec
Hi Mike,
I am using the 2.6.34-rc6,
It seems that the NET_POLL_CONTROLLER will be equal to NETPOLL.
Could you check your Kconfig of NETPOLL?
Thanks,
Dongdong
linux-2.6/drivers/net/Kconfig:
config NETPOLL
def_bool NETCONSOLE
config NETPOLL_TRAP
bool "Netpoll traffic trapping"
de
Hi Mike,
Could you tell us your kernel version?
The KGDBOE didn't be added to lib/Kconfig.kgdb by default.
I am wondering where your KGDBOE come from. :-)
Thanks,
Dongdong
On Wed, May 26, 2010 at 4:07 AM, Mike Frysinger wrote:
> From: Sonic Zhang
>
> If we try to enable KGDBOE but NET_POL
On Fri, Feb 5, 2010 at 3:08 PM, Philippe Auphelle wrote:
> Hi Dongdong,
>
>> Maybe you set a wrong format parms to kgdb, so it uses the default parms.
>
> I don't think so, because if I kgdbwait, then the speed is actually
> what I set on the kernel parm line (eg 115200) when the kernel hits
> its
On Fri, Feb 5, 2010 at 5:49 AM, Philippe Auphelle wrote:
> FWIW, I had a similar problem first time I used kgdb.
> I'm using it to debug modules, butand when I reached my own hard coded
> int 3 in the module, I ended up with a timeout in gdb, andhost /
> target connectivty was lost.
>
> It happens
On Mon, Feb 1, 2010 at 2:05 PM, Jason Wessel wrote:
> Dongdong Deng wrote:
>> On Fri, Jan 29, 2010 at 10:51 PM, Jason Wessel
>> wrote:
>>
>>> echo 3 > /proc/sys/kernel/softlockup_thresh
>>>
>>> And then some kernel code in a thread like:
>>
On Fri, Jan 29, 2010 at 10:51 PM, Jason Wessel
wrote:
> Ingo Molnar wrote:
>> * Jason Wessel wrote:
>>
>>
>>> @@ -118,6 +125,14 @@ void softlockup_tick(void)
>>> }
>>>
>>> if (touch_ts == 0) {
>>> + if (unlikely(per_cpu(softlock_touch_sync, this_cpu))) {
>>> +
On Tue, Jan 26, 2010 at 4:50 PM, Thomas Gleixner wrote:
> On Tue, 26 Jan 2010, Martin Schwidefsky wrote:
>> On Mon, 25 Jan 2010 22:26:39 -0600
>> Jason Wessel wrote:
>>
>> > This is a regression fix against: 0f8e8ef7c204988246da5a42d576b7fa5277a8e4
>> >
>> > Spin locks were added to the clocksour
db's mail list to report this problem.
Thanks,
Dongdong
>
> I know this raises more questions than answers ;-) Let me know what you think.
>
> Thanks,
> -Joel
>
> On Fri, Jan 15, 2010 at 7:17 AM, Dongdong Deng wrote:
>> On Thu, Jan 14, 2010 at 9:58 AM, Joel Ferna
On Thu, Jan 14, 2010 at 9:58 AM, Joel Fernandes wrote:
> On Wed, Jan 13, 2010 at 7:17 AM, Dongdong Deng wrote:
>> On Wed, Jan 13, 2010 at 4:50 AM, Joel Fernandes wrote:
>>> I'm running linux kernel 2.6.30 with kgdb8250 on x86_64
>>> When I set a breakpoint and co
On Wed, Jan 13, 2010 at 4:50 AM, Joel Fernandes wrote:
> I'm running linux kernel 2.6.30 with kgdb8250 on x86_64
> When I set a breakpoint and continue, I get a 'error accessing memory
> address' error:
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> kgdb_breakpoint () at kernel/kgdb
Hi Nick,
Quickly skim your log, I find that:
make install ---> /bin/sh: line 1: ..//.././bfd/../mkinstalldirs:
Permission denied
It seems that the current user no permission to operate some files.
Could you try "sudo make install" ?
Thanks,
DDD
2009/8/10 鄭守謙(Nick Cheng)
> Hi Caz,
> I got
35 matches
Mail list logo
