<apelete>
does anyone know what debug options must be activated in the kernel in order to make the call trace readable and ease debugging ?
<apelete>
there are a lot of options in the "kernel hacking" section of menuconfig, can someone help me select the relevant ones ?
<mth>
maybe CONFIG_DEBUG_KERNEL?
<mth>
that's one of the few debug options I have enabled here and I've got stack traces with symbols
<apelete>
yes, saw that. will begin with that one at least, thanks
arossdotme has joined #qi-hardware
kilae has quit [Quit: ChatZilla 0.9.90.1 [Firefox 23.0.1/20130814063812]]
<wpwrak>
grnbl. i hate it when i fall off a git branch :-(
<larsc>
better watch your steps next time
<wpwrak>
yeah, i kinda wonder how it happens. didn't do anything unusual. and of course, i usually notice such things after i've been happily committing to the headless branch for hours if not days ...
* whitequa1k
glares at this flashing utility
<whitequa1k>
Flash written and verified! jolly good!
<larsc>
wpwrak: git reflog will list all the headless commits
<larsc>
or if you ware still at headless commit you can just recreate the branch name
<wpwrak>
git reflog just shows the entire log. i don't think i lost anything, just "lost" master and then committed on the headless branch until i noticed that something was amiss. then i merged back, but with a surprisingly large number of conflicts. luckily, nothing overly mysterious.
<larsc>
git reflog shows all commits, so if you loose a commit and don't know the id anymore you can still find it in there
<wpwrak>
ah, i see. yes, that could be useful when things get a little worse. thanks !
<larsc>
it is basically a more fancy ls --sort=time .git/objects