Re: Nemiver Errors



Venkatram Tummala <venkatram867 gmail com> a écrit:

[...]

>
> I have attached the log file.
>

Thanks, it was useful.

> Here is some more context. I am trying to use nemiver to debug a
> remote linux kernel.

Okay, this makes more sense. So you launched nemiver on a program that
is not supposed to run on userland, on your local host. When you do
nemiver <a-program>, what it does after loading the program is:
1/it sets a breakpoint in the symbol named "main".
2/it runs the program.

The effect is to stop the execution of the program in the main function
which is what most users want they debug a userland program like that.

> The way i do it using gdb is :
>
> (gdb) file vmlinux
> Reading symbols from /home/vtummala/kernels/linux-2.6.35.6/vmlinux...done.
> (gdb) target remote raptor:8864
> Remote debugging using raptor:8864
> native_safe_halt () at
> /home/vtummala/kernels/linux-2.6.35.6/arch/x86/include/asm/irqflags.h:50
> 50 }
> (gdb)
>

Yup. So here, you tell the debugger to connect to a remote target, and
the local binary you are giving it is "just" for symbolic information
resolution.

You can do the same with Nemiver, by ...

> I found a workaround. If i use nemiver "connect to remote target", specify
> the executable & the remote target, nemiver works fine. I dont if this was
> intended use case.

... just doing this, indeed. This is not a workaround, but rather the
way it is intended to work.

Now, the issue I see is, Nemiver should not have emitted these errors in
the first place. I tried to reproduce your issue by tentatively
modifying the current master code to set a breakpoint into a non
existing symbol at Nemiver startup and it didn't emit the error messages
you are seeing.

>
> In general, if i say "ddd vmlinux" & then specify remote target, it works
> fine. So, i was trying to do the same thing with nemiver instead of ddd.
>

Maybe I should provide a command line for Nemiver too, to attach to a
remote target so that you don't have to do that with the GUI only?

Oh wait, there is a bug opened for that already at
https://bugzilla.gnome.org/show_bug.cgi?id=624630

I'll try to work on this in a not-too-distant future, unless someone
beats me to it :-)

Thank you for your time.

-- 
	Dodji


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]