Closed Bug 80874 Opened 24 years ago Closed 20 years ago

t@1 (l@1) dbx: error in parsing nested blocks ..... (l@X) terminating signal 10 SIGBUS

Categories

(SeaMonkey :: General, defect)

Sun
Solaris
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: timeless, Assigned: timeless)

References

Details

(4 keywords)

mozilla xlib cvs build solaris 7 sparc from (~3hrs old), Forte C++ 5. Debugger: DBX Running Choffman's browser buster and attempting to enable GFX widgets in Preferences Debug. Unfortunately it takes a _long_ time to load mozilla in dbx so I may not be able to reproduce before my build disintegrates. *** Forcing reframe! *** *** Forcing reframe! *** *** Forcing reframe! *** *** Forcing reframe! *** /buster/top100/url.43 WEBSHELL- = 11 /buster/t.html WEBSHELL- = 10 /buster/count.html WEBSHELL- = 9 WEBSHELL- = 8 WEBSHELL+ = 9 WEBSHELL+ = 10 WEBSHELL+ = 11 WEBSHELL+ = 12 *** Forcing reframe! *** *** Forcing reframe! *** /adi/wpni.washingtonpost.com/;kw=;pos=top;sz=468x60;! category=wholesale;tile=1;ord=86705934904679990 0?nocache=true WEBSHELL- = 11 *** Forcing reframe! *** t@1 (l@1) dbx: error in parsing nested blocks ..... (l@X) terminating signal 10 SIGBUS (/opt/SUNWspro/bin/dbx) where dbx: program is not active
it wasn't preferences [well, *** Forcing reframe! *** was, but that's not the crasher] but it did recur and i can't get any useful info. I need advice on how to use dbx I guess...
Status: NEW → ASSIGNED
Depends on: 79119
Summary: *** Forcing reframe! *** t@1 (l@1) dbx: error in parsing nested blocks ..... (l@X) terminating signal 10 SIGBUS → t@1 (l@1) dbx: error in parsing nested blocks ..... (l@X) terminating signal 10 SIGBUS
This looks like it _might_ be a bug in dbx, but I'm not sure. Pinging some of the Sun folks may be your best bet...
dbx: Workshop 5.0 12/15/98 [dbx 5.0] Perhaps I should request we upgrade to Workshop 6...
No longer depends on: 79119
Blocks: 79119
this bug has not been touched since 2001-05-15, therefore this reminder. Reporter could oyu please retest with a current build and let us know if the problem is still present, or if this bug can be closed.
timeless ? Shall we keep this bug open or closed it as WFM ?
Product: Browser → Seamonkey
No further responses from reporter for almost 4 years. Marking as WFM. Reopen if the problem persists with current builds.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.