Hi Valdis
On Wed, Feb 10, 2016 at 2:37 PM, wrote:
>
> See what happens when you do 'echo t > /proc/sysrq-trigger'.
This is exactly what I was needing :) I owe you a beer.
>
> Note that you probably *don't* actually want a trace of *all* tasks (hint -
> what happens on
On Thu, 11 Feb 2016 14:56:32 +0100, Ricardo Ribalda Delgado said:
> > What problem are you trying to solve by getting a trace of everything?
> > (Hint -
> > what meaning does a userspace stack traceback have if you're looking at
> > the corresponding kernel stack trace?)
>
> I was doing:
>
> cat
On Wed, 10 Feb 2016 11:56:40 +0100, Ricardo Ribalda Delgado said:
> I did not explain myself well.
>
> By thread I mean kernel thread, and user thread.
>
> What i want to get is a back trace of ALL the programs running in user
> and kernel space.
See what happens when you do 'echo t >
Hi Anupam
On Wed, Feb 10, 2016 at 10:20 AM, Anupam Kapoor wrote:
>
>
> In a multi-threaded program, gdb by default shows the backtrace only for
> the current thread. To display the backtrace for several or all of the
> threads, use the command thread apply (see thread
I did not explain myself well.
By thread I mean kernel thread, and user thread.
What i want to get is a back trace of ALL the programs running in user
and kernel space.
Your example is a single program, and the trace ends in userspace.
Sorry for the missunderstunding.
On Wed, Feb 10, 2016 at
> [2016-02-10T15:06:30+0530]: "Ricardo Ribalda Delgado" (ricardo-delgado):
,[ ricardo-delgado ]
| Unfortunately not :( But thanks for trying :)
`
seems to work just fine on a trivial program here:
< aside: hopefully, i will not be judged too harshly for c++ :) >
,
| anupam@fatcat
> [2016-02-10T16:26:40+0530]: "Ricardo Ribalda Delgado" (ricardo-delgado):
,[ ricardo-delgado ]
| By thread I mean kernel thread, and user thread.
|
| What i want to get is a back trace of ALL the programs running in user
| and kernel space.
`
d.u.d.e :)
--
kind regards
anupam
> [2016-02-10T14:35:33+0530]: "Ricardo Ribalda Delgado" (ricardo-delgado):
,[ ricardo-delgado ]
| Luckily, the error is gone now :). but I was wondering if there is a
| way to show the backtrace of ALL the threads in the system, which
| could have been a wonderful tool to debug this
Hello
I have been debugging a process that makes a syscall which never
returned. The problem was the interaction between than process and
other kernel threads, due to an error on the way the locks were
designed (my bad).
Luckily, the error is gone now :). but I was wondering if there is a
way to