Bug 6176 – Segmentation Fault

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 6176 - Segmentation Fault

Summary:	Segmentation Fault

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	rp3 (Show other bugs)
Sub Component:
Version:	6.1
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Michael K. Johnson
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-10-21 00:33 EDT by kabir
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-11-18 18:42:06 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description kabir 1999-10-21 00:33:14 EDT

When I run it from Gnome. It crashes.

I get segmentation fault at some process id #.

Comment 1 Michael K. Johnson 1999-10-27 12:13:59 EDT

When this happens, please start a new terminal session and run
gdb /usr/bin/rp3 <pid>
where "<pid>" is the process ID that you are given in the dialog
box that tells you about the crash, and then give gdb the command
bt
which will print out a backtrace.  Give us that backtrace, and we
will likely be able to figure out what went wrong.

Comment 2 Michael K. Johnson 1999-11-04 16:58:59 EST

Here are easier instructions for getting the stack trace:
  gdb /usr/bin/rp3
  r
  bt
Now paste the output into bugzilla for us, and we can look into
the problem.

Thanks,

Comment 3 Michael K. Johnson 1999-11-18 18:42:59 EST

Please try
ftp://people.redhat.com/johnsonm/rp3/rp3-1.0.2.i386.rpm

If that doesn't fix it, then I'll need more information in order
to have any possible hope of fixing this.

Note You need to log in before you can comment on or make changes to this bug.