Opened 8 years ago

Closed 8 years ago

#7263 closed defect (fixed)

'nvram get' without parameters segfaults, brcm47xx

Reported by: Sami Olmari <jaarli@…> Owned by: developers
Priority: low Milestone: Backfire 10.03.1
Component: base system Version: Backfire 10.03
Keywords: nvram, nvram get, segmentation fault Cc:


When I (accidentally) ran command "nvram get" without any parameters in Buffalo whr-hp-g54 cli running 10.03 brcm47xx, it generated "Segmentation fault".

While I know this isn't exactly correct usage of that command, I still believe it shouldn't make an segfault either :p

having any additional parameters does work, no matter is there actually nvram variable by the name of parameter (generates either exit 1 or 0, looked with strace).

I'll also attach what "strace nvram get" spits out here.

Attachments (1)

nvram_get (4.1 KB) - added by Sami Olmari <jaarli@…> 8 years ago.
strace of 'nvram get'

Download all attachments as: .zip

Change History (3)

Changed 8 years ago by Sami Olmari <jaarli@…>

strace of 'nvram get'

comment:1 Changed 8 years ago by Sami Olmari <jaarli@…>

Also "nvram unset" and "nvram set" segfaults without parameters (tested for kicks). So any nvram command that needs a variable but isn't given one will segfail.

comment:2 Changed 8 years ago by jow

  • Resolution set to fixed
  • Status changed from new to closed

Should be fixed with r21288

Add Comment

Modify Ticket

as closed .
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.