./inspectr

, ,

I should have maybe posted this already some time back - but later is better than never. Axel ported the crashlogger inspector to x86 Linux! So here comes a little HowTo run it: First you'll need to download inspectr, save it somewhere and
$ chmod 755 inspectr
Next step is to attach it to the Opera you want to monitor for a crash:
$ ./inspectr <opera_binary_PID>
The <opera_binary_PID> is the ProcessID of the binary you want to monitor - the binary, not the wrapper script (this is easily done wrong). How to detect the PID of the Opera binary?
$ ps aux | grep opera
This will give you a list of all processes called opera that you might need: if you want to monitor the main Opera installation that you started with the command
$ opera& 
you'll need to be looking for something like
/usr/lib/opera/<opera_version>/opera
if, on the other hand, you want to monitor a test version you started from a tarball with
$ ./opera
look out for
./bin/opera
Done! As soon as Opera crashes, inspectr will create a crashlog in its directory. For the procedure on how to report crashers, follow the instructions - note that for compression bzip2 is reccomended (it should be installed on virtually any Linux distro). Update: please always also report which package you are using (static .1, shared .5 or .6).

Example

(just a tiny bit simplified output, for readability):
$ ./opera&
$ ps aux | grep opera
csant 14203 /bin/sh ./opera
csant 14212 ./bin/opera
$ ./inspectr 14212
Using PID 14212

Update

There is now also an official KB article on the topic.

on plaguesipw2200 and ieee80211

Comments

Moose Tuesday, October 18, 2005 7:23:42 PM

Now he should port it to BSD smile

M.

Pistos Tuesday, November 15, 2005 3:42:42 PM

I am running on Gentoo Linux and when I tried to attach to the process, it froze my Opera window(s). Is it supposed to return to the shell prompt after outputting "Using PID ####" ?

Claudio Santambrogiocsant Tuesday, November 15, 2005 8:14:00 PM

It shouldn't freeze Opera - which commands did you exactly run?
It will wait at "Using PID ####" until a) Opera crashes, b) Opera exits cleanly, or c) you terminate inspectr with ^C

steviepafrusurewa Sunday, December 4, 2005 11:10:03 PM

I think it's worth mentioning that this is an Intel x86 binary. "Linux" isn't very specific.

Claudio Santambrogiocsant Sunday, December 4, 2005 11:50:28 PM

My bad - thanks for pointing this out.
/c smile

steviepafrusurewa Monday, December 5, 2005 12:20:20 AM

Thanks. I just pointed it out because I actually was dumb enough to try to run it on a Debian/PowerPC install to resolve an Opera crash; I thought it was a script of some sort. :-)

Denilson Figueiredo de SáCrazyTerabyte Monday, February 13, 2006 2:17:47 PM

No, it did not work for me. Opera crashed and inspectr did NOT log it. In addition, Opera froze a lot of times while inspectr was running. No solution to this, unless manually kill all opera processes.

Maximilian Haackcoffeejunk Sunday, February 26, 2006 9:53:13 AM

for me inspector doesn't work either.. i use opera 9 weekly build 1656, and it crashes often.. i can start ./inspector opera without any problems, but if opera crashes inspector wont log any errors.

Claudio Santambrogiocsant Sunday, February 26, 2006 10:12:25 AM

coffejunk, have you read the instructions? Starting `./inspectr opera' is bound to lead into trouble, that doesn't really work as reliable yet - that is also the reason why it was not mentioned anywhere in my instructions wink

rwf Thursday, February 28, 2008 8:40:35 PM

Linspector v2.2
---------------
Usage:
Crash logging for already running process: inspectr <process name or ID>
Memory guarding: inspectr <executable file name>


1. Is this the current version?

2. How do I do 'Memory guarding'. I did the following while opera was running:
inspectr /usr/local/lib/opera/9.50-20080221.6/opera
Using PID 28284


Is it really doing Memory guarding or Crash logging? Thank you.

nidelius Monday, January 19, 2009 10:58:27 AM

Is there also a 64bit version of the inspector file?

Claudio Santambrogiocsant Monday, January 19, 2009 7:55:14 PM

Yes. In the directory listing you'll find inspec64 (64-bit linux), inspbsd (intel-freebsd) and insbsd64 (64-bit freebsd).

João EirasxErath Wednesday, February 18, 2009 9:29:48 PM

Simpler
opera &
inspectr $!
Or a bash script
#!/bin/bash
opera $@ &
inspectr $!

Kyle Bakerkyleabaker Thursday, February 26, 2009 11:55:06 PM

I posted a simple script as well a little while back in my blog:
http://kyleabaker.com/2009/02/10/crash-logging-opera-with-inspector-iixii-for-linux/

#!/bin/sh

opera=`ps aux | grep opera$ | awk '{print $2}'`
if [ "$opera" != "" ]; then
./inspectr $opera
fi

pgweiss Wednesday, April 29, 2009 3:32:44 AM

The docs say how to get a freeze log using Windows inspectr. Is there a way to do it using Linux inspectr?

Claudio Santambrogiocsant Wednesday, April 29, 2009 12:04:20 PM

pgweiss, yes - while opera freezes do a
kill -11 <opera_pid>

and you'll get a freeze log smile

maniel Saturday, June 27, 2009 2:12:32 PM

and what if only -9 [kill] signal is able to terminate hanged opera? for me -11 does nothing when opera hangs on flash [on other hand it's rare, but it's only hang type I've encountered;-)]
EDIT: I'm using 10.00 build 4453 qt4 86_64 with inspec64, and it's really weird, after trying kill -11 while normally using opera it doesn't harm opera, but inspectr is writing log

Write a comment

You must be logged in to write a comment. If you're not a registered member, please sign up.

February 2012
S M T W T F S
January 2012March 2012
1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29