Definitely.

I read that you had a crash and you didn't know why.

It is a good idea to run pharo under gdb so you can do a bt (backtrace) and see where it bombed.

You can inspect parameters etc. Usually this is revealing of the problem when I do like that.

Check http://stackoverflow.com/questions/6121094/how-do-i-run-a-program-with-commandline-args-using-gdb-within-a-bash-script

Like��

gdb -ex=r --args pharo-vm/pharo Pharo.image

(not sure this is all right, but you'll figure it out).

I also like to use a debug or assert VM so that I get all debugging symbols information.

Alternatively, connect to a running Pharo with gdb -p PID

I usually do that from something like Code::Blocks with an assert VM + source code around for whatever library I am trying to use from UFFI. Works nicely. Especially when you put a breakpoint before a crashing site, allowing you to see the stackframes etc.

With gdb command line, it is worth knowing about frames:��http://www.delorie.com/gnu/docs/gdb/gdb_44.html

Namaste,

Phil

On Wed, May 17, 2017 at 2:08 PM, Guillermo Polito <guillermopolito@gmail.com> wrote:

Thanks Rajula :)

This is cool!

On Wed, May 17, 2017 at 1:38 PM, Rajula Vineet <Vineet.Reddy@iiitb.org> wrote:
Hi all,

I am working on improving pharo command line as a part of my GSoC project. I
have been looking at different current working directory implementations. I
have written a�� blog post
<https://vineetreddy.wordpress.com/2017/05/17/pwd-vs-getcwd/>�� on it. It
would be of great help, if you can take a look and give your feedback.

Rajula

--
View this message in context: http://forum.world.st/Current-working-directory-tp4947453.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

--

��

Guille Polito

Research Engineer

French National Center for Scientific Research - http://www.cnrs.fr

Web: http://guillep.github.io

Phone: +33 06 52 70 66 13