Ok -- I tried the same silly maneuver w/ a few other apps, and no crashes.
Thanks for explaining what "selection" is for, btw. I have to admit ignorance of the deeper parts of the OS, such as snmpget. It appears to be called because (don't ask!) I have to print thru an internal corporate firewall, so I call the IP addresses of various printers directly. In any case, yeah, I'll avoid sleeping while my mouse button is depressed :-) . thanks Carl -----Original Message----- From: Simon Urbanek [mailto:[email protected]] Sent: Thu 2009-01-15 2:14 PM To: David Winsemius Cc: Witthoft, Carl G (ST); CarlAtHome; [email protected] Subject: Re: [R-SIG-Mac] timeout bug in print dialog On Jan 15, 2009, at 14:03 , David Winsemius wrote: > > On Jan 15, 2009, at 7:39 AM, Witthoft, Carl G (ST) wrote: > >> Had a document open in the R.app editor and selected Print. Due to >> daydreaming, I held the mouse down for maybe 30 seconds with the >> printer drop-down list open. R crashed -- here's what was >> displayed on the console >> >> >> *** caught bus error *** >> address 0x84, cause 'non-existent physical address' >> >> Possible actions: >> 1: abort (with core dump, if enabled) >> 2: normal R exit >> 3: exit R without saving workspace >> 4: exit R saving workspace >> No log handling enabled - turning on stderr logging >> snmpget: Timeout >> snmpget: Timeout >> 2009-01-15 07:33:16.763 R[401] tossing reply message sequence 5 on >> thread 0x11b0b80 >> Rgames: >> Selection: >> >> ("Rgames" is my prompt. I dunno where "Selection" came from) > > "Selection:" is asking you to type an integer between 1 and 4 and > hit return. > > Looks like you overflowed a buffer, and the system threw an error at > R. I held down the print button with the mouse and then moved the > mouse off the button. The Print dialog box then said I had queued up > 1443 pages and the spinning rainbow icon persisted. Is that what you > mean by" crash"? My guess is that a print buffer got too full. > > If you went into your doctor and said "It hurts when I poke a pencil > in my leg", it might prompt a reply, "Don't do that". > FWIW the crash is deep in Apple's print dialog code (and it's funny to see that it's all legacy Carbon), so I would be inclined to send this to Apple as it's more likely their bug ... [although you seem to have a rather funky setup judging by those snmpget timeouts ...]. Nonetheless, thanks for reporting. Cheers, S [[alternative HTML version deleted]] _______________________________________________ R-SIG-Mac mailing list [email protected] https://stat.ethz.ch/mailman/listinfo/r-sig-mac
