Re: missing top menu

[John D <smappersmapper gmail com>]

Bill Martin <Bill Martin    > writes:

> 
> Hello Dodji,
> 
> I was just noticing that the help screens say that there is no way to start a 
remote debug session from the
> command line, which must be outdated info, since you just told me how to do 
it...but what I was wondering was
> if it would be reasonable to make a tcp/ip setting "sticky", so that it would 
automatically connect on
> startup of Nemiver, if there was something set for these variables. This idea 
came up because I'm planning
> to use OpenOCD and a cheap jtag box instead of thrashing with getting an Arm 
version of gdbserver
> integrated into the code I'm working on. So it will always be the same 
settings no matter the actual target
> addresses. OpenOCD just seems like a really good idea. For now I can certainly 
just do a one-liner shell
> script to get what I'm after, but that doesn't seem to translate to starting 
up with the "bug-in-a-bottle" icon.
> 
> Best Regards,
> Bill Martin
> 
> -----Original Message-----
> From: nemiver-list-bounces <at> gnome.org [mailto:nemiver-list-bounces <at> 
gnome.org] On Behalf Of Dodji Seketeli
> Sent: Thursday, August 16, 2012 9:37 AM
> To: The mailing list of the Nemiver project
> Subject: Re: missing top menu
> 
> Bill Martin <Bill.Martin <at> memjet.com> a Ãcrit:
> 
> > Well, it is solved. One of those embarrassing "DUH!" things, the menu
> > is there as it should be, but is not visible until the mouse pointer
> > is in the region of the screen.
> 
> Ah, I see.  This is the "Application Menu" in Ubuntu, I guess.  At any point 
in time, the menu of the currently
> selected application is located at the top of the screen, in their "Unity" 
desktop environment.
> 
> > Anyway, I'm now on to the next thing, figure out how to debug an
> > embedded arm target, if that is possible.
> 
> It should be possible, using the support of gdbserver.  For that, you need to 
have gdbserver on the target,
> properly started and listening on a given IP address and port HOST:PORT.  You 
also need to have a gdb cross
> compiled for arm on your host (I'll call it arm-cross-gdb), as well as the 
binary you want to debug (I call
> that the inferior) be present on your host (as well as on the target, of 
course).
> 
> Then you can do:
> 
>     nemiver --gdb-binary=/patch/arm-cross-gdb --remote=<HOST:PORT> 
/path/to/inferior/built/for/arm
> 
> You can make Nemiver persistently use the arm-cross-gdb binary by going into 
the menu edit -> preferences,
> select the "debugger" tab and specify the path to the arm-cross-gdb.  
Subsequent invocations of nemiver
> will just have to be:
> 
>     nemiver --remote=<HOST:PORT> /path/to/inferior/built/for/arm
> 
> 
> > Thanks very much for providing this nice tool!
> 
> You are welcome.
> 
> --
>                 Dodji
> _______________________________________________
> nemiver-list mailing list
> nemiver-list <at> gnome.org
> https://mail.gnome.org/mailman/listinfo/nemiver-list
> 
> 
> The information contained in this email message is confidential information 
and/or privileged and
> intended only for the use of the individual or entity named above. If the 
reader of this message is not the
> intended recipient, or the employee or agent responsible to deliver it to the 
intended recipient, you are
> hereby notified that any dissemination, distribution, or copying of this 
communication is strictly
> prohibited. If you have received this communication in error, please destroy 
it and remove it
> immediately from your PC and server, and notify us by return email that it was 
received in error. Thank you.
> _______________________________________________
> nemiver-list mailing list
> nemiver-list <at> gnome.org
> https://mail.gnome.org/mailman/listinfo/nemiver-list
> 

I don't see a way to point to symbols; We need  pull-down to include a pathname 
to various symbols : similar to gdb -s