From: Ulf Carlsson <ulfc@bun.falkenberg.se>
To: Linux SGI <linux@cthulhu.engr.sgi.com>
Subject: GDB
Date: Mon, 22 Mar 1999 16:47:06 -0500 [thread overview]
Message-ID: <19990322164706.A27372@bun.falkenberg.se> (raw)
Hi,
I'm having some problems with gdb for mips. I can't examine core files since gdb
itself dumps core files when I try start gdb (gdb nsgsml core). Are there other
ways to check where a program crashes (except for printf()s)? It isn't possible
to run nsgsml in gdb either, or at least it doesn't provide the information I
want.
It's also tricky to debug where gdb fails because it just dumps another core
when I try to debug the core file gdb dumps :)
By the way, I have received a new Indy from SGI (that's why I'm back in action).
But the monitor was not working so I had to take the machine to the support
center in Sweden, which I did last Friday. They replaced the monitor so
everything works fine now. Thanks Nancy!
FYI I've fixed /dev/graphics now (thanks for making it a module at first place
Alex!). The code was really broken. I'll commit that stuff sometime when I don't
experience too much CVS problems.. (CVS is really bad from here..)
I've applied for being an X developer now as well (X was the real reason for
fixing /dev/graphics). Maybe I can remove the abscence of X servers if it's so
easy to port the IBM8514 driver as everyone says it is.
- Ulf
next reply other threads:[~1999-03-22 15:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-22 21:47 Ulf Carlsson [this message]
1999-03-22 23:10 ` GDB Thomas Bogendoerfer
-- strict thread matches above, loose matches on Subject: below --
2006-07-31 23:41 gdb Ratin Rahman (mratin)
2006-07-31 23:41 ` gdb Ratin Rahman (mratin)
1999-07-25 12:34 GDB Ralf Baechle
1998-11-05 1:30 GDB ralf
1998-11-06 20:24 ` GDB Thomas Bogendoerfer
1998-11-08 23:50 ` GDB ralf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19990322164706.A27372@bun.falkenberg.se \
--to=ulfc@bun.falkenberg.se \
--cc=linux@cthulhu.engr.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox