On Sun, Jul 28, 2013 at 09:16:15AM +0000, Plüss Tobias TA.E.1001 wrote: > So what I did so far is to just step trough the plain assembly code, > without any debug symbols, and you can imagine, it's very difficult > to get an idea what this thing is doing :-)
In cases like these I tend to search for a group of instructions in the output of objdump -d to get the name of the previous label. If you are able to step through the code, could you determine which instruction causes the exception? Daniel _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
