I'm in the Graph View mode of IDA Pro and I'm looking at a function. This function calls another function, and when I click on that function name, I'm taken to its assembler code.
My problem is that I want a simple way to get back to the function I came from, the caller function. I can do it with jump to xref to but I was hoping for a simpler "go back" or something (like Eclipse has). Is there such a feature available?
Esc key, or navigation buttons on the toolbar.
Related
I am writing some scripts using BGI and I am facing an interesting problem I do not know how to solve. Let us say I want to create a log pannel, where I want to write on window(using outtextxy() function) some events that happened in sofware (like delete, create etc). But I do not know how.
So far, I thought of floodfill the entire area where the text has been written, but it seems that is not working.
floodfill(3.7*width_rectangle+1, height_rectangle*14.3+1, WHITE);
setcolor(BLACK)
outtextxy(x,y, char*);
I tried some other things, like having a stack that stores all logs and when a new event happens, I take last element, I write it in BLACK again (to overwrite the existing one) and then a push the event to the stack. But it seems that this is not working too.
Can anybody suggest me a way to write text over another text in BGI?
I have created a demo app that applies multiple filters to an image (it is inside the project) and shows buttons in a UIScrollView with that images set as a background image. So, all the logic happens in a method that is called right from viewDidLoad. I'm not using any threading mechanism, so all the work is happening on the main thread.
I'm using Instruments, specifically Time Profiler to find out why the app launches so slow (it is obvious, but I would like to see it in Time Profiler).
When I run it I get the following result in the detail panel (in the root):
And when I press the arrow to see the actual code I get the following:
And this is for every filter operation.
Shouldn't the panel show the actual method inside of which I do filtering?
The main function is not the cause of your app being slow. In your screenshot the listing for main says you spent 0 seconds in main.
The Time Profiler instrument records the call stack 1000 times per second. The main function is the starting point for your app. That means main is going to be on the call stack most of the time your app is running, even though your app is not in main most of that time. The main function being on the call stack is the reason for the 649 ms and 95.5% listings in your screenshot.
Do not worry about the listing for the main function. You have no control over main.
If you want to find your functions in the call tree, select the Invert Call Tree and Hide System Libraries checkboxes. Selecting those checkboxes makes it easier to find your code in the call tree.
In the program I am writing, I created an OLEObject to connect to a webpage in Internet Explorer that results in an automatic pop-up prompting me for my credentials.
I've been trying to avoid having to switch tabs and manually click OK by instead sending the "ENTER" keystroke to the window using Sybase's keybd_event subroutine : http://www.sybase.com/detail?id=47760
I declared the subroutine as an External Global Function and added the code where it was needed. The interesting thing is is that the program successfully presses the OK button in the pop-up window when I step through each line in debugger mode, but it fails to do so when I compile and run it.
Could anyone give any suggestions as to how to fix this? Or perhaps propose an alternative method entirely?
Thanks!
I'm not clear if you are using the built in Inet, InternetResult, InternetData objects in PB, but if you are I think you use the PostURL to do something like that. Then use the GetUrl to read a webpage into the Inet object. It's been a long time since I've used this, apologize if this leads you down the wrong path.
I was having temporary difficulties setting the icon of a window in my C program to a stock icon, and I almost asked how to do it, but then I created the GdkPixbuf I needed like this:
gtk_widget_render_icon(GTK_WIDGET(window),GTK_STOCK_CONVERT,-1,NULL)
The last argument is described by the documentation as "render detail to pass to theme engine. [allow-none]" (here). Since I have no idea what an appropriate value for that might be, I set it to NULL and hoped it would work. It did work, but now I want to know why.
What is this value supposed to be? Is there any possible repercussion if I leave it as NULL?
From the documentation you linked to:
detail should be a string that identifies the widget or code doing the rendering, so that theme engines can special-case rendering for that widget or code.
The way I interpret that is that you might set it to "Wutaz-window-icon" and then if theme writers needed to write a special case for your application, they could match that string.
However, the point is moot; as #MrEricSir points out, the function is deprecated.
I am using CEF3 and want to hardcode and disable the address bar of the browser. I am not finding the right place in the code base to do the same. Any pointers would be of great help.
Either through the C++ or Javascript methods would help.
Thanks,
Ashwin
Are you using cefclient? I don't think there's a clean way to turn it off in the standard version of cefclient.
However, in the brackets-shell fork of cefclient there's a #define you can use to toggle it on/off cleanly. Just search for references to SHOW_TOOLBAR_UI (it's only used in four files). I'm guessing it wouldn't be too hard to manually apply those diffs back onto a clean copy of cefclient (you probably don't want to take the brackets-shell fork as-is – it's not very generic).
You can build a CEF application using the binary, just like the WIKI does. Please see the github project for a reference https://github.com/acristoffers/CEF3SimpleSample
I realize this question is old but I had the same question and found the solution.
In the cefclient example, the address bar is drawn within the RootWindowGtk::CreateRootWindow function.
Delete the gtk_container_add function call that adds the GtkToolItem* corresponding to the address bar and the address bar will be gone.