I tried to enable the Full Symbolic/Source Debugging support option in the
kernel hacking section, but no new info was displayed in the crash. Is this
only if I connect via gdb to get the symbolic stack?
I then tried to build with BusyBox support. But I get the following build error.
busybox_u
Thanks for the info. I'll try it when I get home tonight and see if that fixes
the problem. I'll see if I can track down why init would be crashing.
g
On Mar 1, 2010, at 9:39 AM, Dan Snyder wrote:
> Hi Greg
>
> I believe I had the same problem. Rather than trying to fix init, I disabled
> it
Hi Greg
I believe I had the same problem. Rather than trying to fix init, I disabled
it, and enabled busybox's init support instead. I recall getting the same
Access Exception error from the dhcp client as well, and used the same
solution. Maybe if you're less lazy than I am, you can fix the
Hi uclinx-list,
just now I'm looking for __the__ git repository with primary and active
development for Xilinx Microblaze porting. There are more than one. Why?
What is the main different between the git repositories at:
http://git.xilinx.com/cgi-bin/gitweb.cgi
http://developer.petalogix.com/git
