public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@ecoscentric.com
To: ecos-bugs@sources.redhat.com
Subject: [Bug 1000253] segmentation fault error
Date: Tue, 28 Mar 2006 13:27:00 -0000	[thread overview]
Message-ID: <20060328131347.75B61DC8042@snape.ecoscentric.com> (raw)

http://bugzilla.ecoscentric.com/show_bug.cgi?id=1000253


mr_princepaul@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |MODIFIED
          Component|C library                   |ecosconfig




------- Additional Comments From mr_princepaul@yahoo.com  2006-03-28 14:13 -------
[rng@Linux prince]$ gdb out
GNU gdb Red Hat Linux (5.3post-0.20021129.18rh)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...
(gdb) r
Starting program: /home/rng/prince/out

Program received signal SIGSEGV, Segmentation fault.
<function called from gdb>
(gdb) bt
#0  <function called from gdb>
(gdb)

-- 
Configure bugmail: http://bugzilla.ecoscentric.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.


             reply	other threads:[~2006-03-28 13:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 13:27 bugzilla-daemon [this message]
2006-03-28 15:55 bugzilla-daemon

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=20060328131347.75B61DC8042@snape.ecoscentric.com \
    --to=bugzilla-daemon@ecoscentric.com \
    --cc=ecos-bugs@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).