Bug 4841 - Debug Window aborts when debugging bash
Summary: Debug Window aborts when debugging bash
Status: RESOLVED INVALID
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Rick Moseley
URL:
Keywords:
Depends on:
Blocks: 1633 3620
  Show dependency tree / graph
 
Reported: 2007-07-25 16:11 UTC by Rick Moseley
Modified: 2007-08-13 17:51 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

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

Note You need to log in before you can comment on or make changes to this bug.
Description Rick Moseley 2007-07-25 16:11:27 UTC 
After bringing up the Debug Window with bash and bash-debuginfo has been
installed and then pulling up the shell.c source(frame #14), it aborts when
moving the cursor over a variable.  The message I get is just "Aborted" but if I
do a "ulimit -c unlimited" I get a core dump and running fstack on it shows me
this backtrace:

Exception in thread "main" java.lang.NullPointerException
   at frysk.symtab.SymbolFactory.getSymbol(SymbolFactory.java:65)
   at frysk.stack.RemoteFrame.getSymbol(RemoteFrame.java:233)
   at frysk.stack.Frame.toPrint(Frame.java:122)
   at frysk.stack.StackFactory.printStackTrace(StackFactory.java:117)
   at frysk.stack.StackFactory.printTaskStackTrace(StackFactory.java:104)
   at frysk.util.StacktraceAction.printTasks(StacktraceAction.java:151)
   at
frysk.util.StacktraceAction.allExistingTasksCompleted(StacktraceAction.java:196)
   at frysk.proc.ProcCoreAction.<init>(ProcCoreAction.java:60)
   at frysk.bindir.fstack.stackCore(fstack.java:142)
   at frysk.bindir.fstack.access$1(fstack.java:138)
   at frysk.bindir.fstack$2.parseCores(fstack.java:162)
   at frysk.util.CommandlineParser.doParse(CommandlineParser.java:173)
   at frysk.util.CommandlineParser.parse(CommandlineParser.java:112)
   at frysk.bindir.fstack.main(fstack.java:239)
Comment 1 Rick Moseley 2007-08-01 20:01:42 UTC 

*** This bug has been marked as a duplicate of 4631 ***
Comment 2 Rick Moseley 2007-08-13 17:17:29 UTC 
This is not a duplicate of 4841.  It appears to be Fedora 7 related as I can get
it to work on Fedora 6/x86_64.
Comment 3 Rick Moseley 2007-08-13 17:38:16 UTC 
Now when I run "fstack -a" I get this:

./build/frysk-core/frysk/bindir/fstack -a core.9822 
Task #9822
#0 0x00220802 in [unknown] from /usr/lib/libgtkjava-2.8.so
#1 0x00000000 in [unknown] from Unknown
Task #9823
#0 0x00220802 in [unknown] from /usr/lib/libgtkjava-2.8.so
#1 0x00000000 in [unknown] from Unknown
Task #9824
#0 0x00220802 in [unknown] from /usr/lib/libgtkjava-2.8.so
#1 0x00000000 in [unknown] from Unknown

I have debuginfo loaded for all of the packages frysk uses too including glibc:

rpm -qa | grep debuginfo | sort
atk-debuginfo-1.18.0-1.fc7
audit-debuginfo-1.5.3-1.fc7
bash-debuginfo-3.2-9.fc7
cairo-debuginfo-1.4.4-1.fc7
cairo-java-debuginfo-1.0.5-7.fc7
coreutils-debuginfo-6.9-2.fc7
expat-debuginfo-1.95.8-9
fontconfig-debuginfo-2.4.2-3.fc7
freetype-debuginfo-2.3.4-1.fc7
gcc-debuginfo-4.1.2-12
glib2-debuginfo-2.12.11-1.fc7
glibc-debuginfo-2.6-3
glibc-debuginfo-common-2.6-3
glib-java-debuginfo-0.2.6-8.fc7
gtk2-debuginfo-2.10.11-7.fc7
gtk2-engines-debuginfo-2.10.0-3.fc7
libglade2-debuginfo-2.6.0-3.fc7
libglade-java-debuginfo-2.12.5-6.fc7
libgnome-java-debuginfo-2.12.4-6.fc7
libgtk-java-debuginfo-2.8.7-4.fc7
libpng-debuginfo-1.2.16-1.fc7
libvte-java-debuginfo-0.12.1-7.fc7
libX11-debuginfo-1.0.3-8.fc7
libXau-debuginfo-1.0.3-1.fc7
libXcursor-debuginfo-1.1.8-1
libXdmcp-debuginfo-1.0.2-2.fc7
libXext-debuginfo-1.0.1-2.1
libXfixes-debuginfo-4.0.3-1
libXi-debuginfo-1.0.4-1
libXinerama-debuginfo-1.0.2-1.fc7
libxml2-debuginfo-2.6.28-2
libXrandr-debuginfo-1.2.0-3.fc7
libXrender-debuginfo-0.9.2-1.fc7
pango-debuginfo-1.16.4-1.fc7
zlib-debuginfo-1.2.3-10.fc7
Comment 4 Rick Moseley 2007-08-13 17:51:01 UTC 
Screwed this one up.  I'll re-enter it with the salient info.