* About displaced-stepping function
@ 2008-08-21 12:04 teawater
2008-08-21 12:24 ` Michael Snyder
2008-08-21 17:11 ` Pedro Alves
0 siblings, 2 replies; 4+ messages in thread
From: teawater @ 2008-08-21 12:04 UTC (permalink / raw)
To: gdb
Hi guys,
I used GDB cvs version to debug the KGDB and got a memory error.
I found that "displaced-stepping" function cause this error. And when
I use command "maintenance set can-use-displaced-stepping 0" close
this function. Everything is OK.
Did anyone meet this bug too?
Thanks,
teawater
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: About displaced-stepping function
2008-08-21 12:04 About displaced-stepping function teawater
@ 2008-08-21 12:24 ` Michael Snyder
2008-08-21 17:11 ` Pedro Alves
1 sibling, 0 replies; 4+ messages in thread
From: Michael Snyder @ 2008-08-21 12:24 UTC (permalink / raw)
To: teawater; +Cc: gdb
teawater wrote:
> Hi guys,
>
> I used GDB cvs version to debug the KGDB and got a memory error.
> I found that "displaced-stepping" function cause this error. And when
> I use command "maintenance set can-use-displaced-stepping 0" close
> this function. Everything is OK.
> Did anyone meet this bug too?
I haven't...
What target arch (386?)
What gdb version (cvs head?)
What linux version, kernel version?
In what context did the memory error occur (steps to reproduce)?
Can you run the experiment with "set debug remote on" and send the log?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: About displaced-stepping function
2008-08-21 12:04 About displaced-stepping function teawater
2008-08-21 12:24 ` Michael Snyder
@ 2008-08-21 17:11 ` Pedro Alves
2008-08-21 17:19 ` Daniel Jacobowitz
1 sibling, 1 reply; 4+ messages in thread
From: Pedro Alves @ 2008-08-21 17:11 UTC (permalink / raw)
To: gdb; +Cc: teawater
On Thursday 21 August 2008 03:06:14, teawater wrote:
> Hi guys,
>
> I used GDB cvs version to debug the KGDB and got a memory error.
> I found that "displaced-stepping" function cause this error. And when
> I use command "maintenance set can-use-displaced-stepping 0" close
> this function. Everything is OK.
> Did anyone meet this bug too?
>
Does debugging with against KGDB use the same gdbarch as debugging
a linux app? Is there no separate OSABI or something?
This is probably displaced stepping on x86 trying to use the
entry point as scratch space, but it's most likely not possible
to do that.
--
Pedro Alves
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: About displaced-stepping function
2008-08-21 17:11 ` Pedro Alves
@ 2008-08-21 17:19 ` Daniel Jacobowitz
0 siblings, 0 replies; 4+ messages in thread
From: Daniel Jacobowitz @ 2008-08-21 17:19 UTC (permalink / raw)
To: Pedro Alves; +Cc: gdb, teawater
On Thu, Aug 21, 2008 at 11:38:03AM +0100, Pedro Alves wrote:
> Does debugging with against KGDB use the same gdbarch as debugging
> a linux app? Is there no separate OSABI or something?
There's no separate OSABI; if you build the kernel with a Linux
toolchain it's a generic static application.
--
Daniel Jacobowitz
CodeSourcery
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-08-21 11:29 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-08-21 12:04 About displaced-stepping function teawater
2008-08-21 12:24 ` Michael Snyder
2008-08-21 17:11 ` Pedro Alves
2008-08-21 17:19 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox