Ant wrote:
(no debugging symbols found)
(gdb)
Now what? I don't know how to use this gdb thing. :(
I don't know much more there either but the next step should be entering
run. Then, for crash bugs, the next command after that would be bt
for getting a backtrace. Since in your case SM
On 03/17/2009 06:15 PM, Phillip Pi wrote:
On 3/17/2009 3:46 PM PT, Jens Hatlak wrote:
Ant wrote:
(no debugging symbols found)
(gdb)
Now what? I don't know how to use this gdb thing. :(
I don't know much more there either but the next step should be entering
run. Then, for crash bugs,
NoOp wrote:
On 03/17/2009 06:15 PM, Phillip Pi wrote:
On 3/17/2009 3:46 PM PT, Jens Hatlak wrote:
Ant wrote:
(no debugging symbols found)
(gdb)
Now what? I don't know how to use this gdb thing. :(
I don't know much more there either but the next step should be entering
run. Then, for crash
On 03/17/2009 06:40 PM, Leonidas Jones wrote:
NoOp wrote:
On 03/17/2009 06:15 PM, Phillip Pi wrote:
On 3/17/2009 3:46 PM PT, Jens Hatlak wrote:
Ant wrote:
(no debugging symbols found)
(gdb)
Now what? I don't know how to use this gdb thing. :(
I don't know much more there either but the
Weird!! I no longer have freeze ups after saving something. I didn't
change anything! Maybe apt-get update and upgrade changed something
recently. I will follow-up if it happens again. Computers are strange!
--
It doesn't matter what your DD manual says, you did not get 5
experience points for
On 3/16/2009 9:39 AM PT, Philip Chee wrote:
Since I had to dump Debian's IceApe a few weeks ago, I had to install
SeaMonkey (SM) v1.1.4 from
seamonkey-1.1.14.en-US.linux-i686.installer.tar.gz into
/home/Programs/seamonkey/ ... Mostly everything works, but I noticed
saving files cause SM to
On 3/16/2009 9:39 AM PT, Philip Chee typed:
Use the -debug command line switch.
seamonkey -debug
$ ./seamonkey --debug
./run-mozilla.sh -g ./seamonkey-bin
MOZILLA_FIVE_HOME=.
LD_LIBRARY_PATH=.:./plugins:/usr/local/lib/mre/mre-1.1.14
DISPLAY=:0.0
7 matches
Mail list logo
